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.
375bf4316f68101e82be31a4f82e5141e63ee975a54da4b2f11629e5d51ff480
Both payments are on their chains and locked to the same secret hash 16aac3d8d82fb1c22277d4027a7e6915b982b438, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 375bf4316f68101e82be31a4f82e5141e63ee975a54da4b2f11629e5d51ff480
- MakerPaymentSpent: a409ab361f4c64e9a459a3b04c59da56c045535d2ff519c0ee153110f52af55e
57e0244382ca7b39c412596da88aad616f74c27776bd9721e6ac44c055f683cd
Both payments are on their chains and locked to the same secret hash 16aac3d8d82fb1c22277d4027a7e6915b982b438, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 238f82a3ea7cc280ea7753035fe24493d6c46aca7069357a7757af9d8153ecb9
- TakerPaymentSent · TakerPaymentReceived: 57e0244382ca7b39c412596da88aad616f74c27776bd9721e6ac44c055f683cd
- TakerPaymentSpent: 557387c6500b55763d50aa1e10e3eb8846c5e662accf08bcfe358f80015aff2d
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.