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.
c2002e46e36b6118863fa177e0f3c832ac5772c33b0e81101a53793aabe46ae9
Both payments are on their chains and locked to the same secret hash f7c82229ad47d38ca19317f26523e58c20f67795, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c2002e46e36b6118863fa177e0f3c832ac5772c33b0e81101a53793aabe46ae9
- MakerPaymentSpent: 92cd750aad34a18f27652b9523d7b38fe24ddbd6019ac38f628a36cb02c17250
6a0ecbde556749c62d855d3287f8e2a259738ed40a127d2e9ec580ba176df673
Both payments are on their chains and locked to the same secret hash f7c82229ad47d38ca19317f26523e58c20f67795, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 91a71c7c28a38a2ecee7847a2a4b9fc26fab18534a34830d62b0b30bf2df9009
- TakerPaymentSent · TakerPaymentReceived: 6a0ecbde556749c62d855d3287f8e2a259738ed40a127d2e9ec580ba176df673
- TakerPaymentSpent: 4f70925572c22bfea518e230f3151c7aa4071b588265ba677dbee2e0b1c88fc5
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.