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.
14659ca8aa8b8c281060fb33b3b58045ecbe1ea701934045583b617e61fe1115
Both payments are on their chains and locked to the same secret hash badf22ce3b4e65b75778f7ef6c514357d964c06d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 14659ca8aa8b8c281060fb33b3b58045ecbe1ea701934045583b617e61fe1115
- MakerPaymentSpent: 37604419ff4c28a5cdb9c5aabe7f433e1cb10fef75c6df6793c33b2aff87af48
6b186651c2b24416f033d94aad4b0a61b80569c255627a8c9d267d4f574091dd
Both payments are on their chains and locked to the same secret hash badf22ce3b4e65b75778f7ef6c514357d964c06d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9b178f9d2d18a09dd0c0179584a18746d7fe2a18233859934933003bddb37d63
- TakerPaymentSent · TakerPaymentReceived: 6b186651c2b24416f033d94aad4b0a61b80569c255627a8c9d267d4f574091dd
- TakerPaymentSpent: 998f5a5a89b33815cec73025e13525abeab808f3ff3dcb6f2e7b885bc2a31690
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.