An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
92635fb3e7e1448ea69c54bfca240785d05417d34d77d8b5f9f433a87d4678af
Both payments are on their chains and locked to the same secret hash edde0af8bceb9208e3d78fe229281497d4e18a04, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 92635fb3e7e1448ea69c54bfca240785d05417d34d77d8b5f9f433a87d4678af
- MakerPaymentSpent: 96985e89cb8b98635a5879ed2c43a1f6b455422c208156d7cabf0ebef4863efc
cd92b25b2fc6be45350bd2044334cffa62e6d502cce5a638329b2c56bf7eb3ef
Both payments are on their chains and locked to the same secret hash edde0af8bceb9208e3d78fe229281497d4e18a04, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e759e393049074e43e94a947c5614aa9f365f71762536ba0fc4cbd008e392e8b
- TakerPaymentSent · TakerPaymentReceived: cd92b25b2fc6be45350bd2044334cffa62e6d502cce5a638329b2c56bf7eb3ef
- TakerPaymentSpent: 6d70170fca2ff3ceb2ebb15b1527427f3fc41daaabafd267fee06b9d99841e61
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.