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.
4e29529a2086773d78badf5969cbcc07a80cad2f35cc156b477e61a9c01a0985
Both payments are on their chains and locked to the same secret hash f4002d44d2df7c5cee7ffce390c8d685a2e979ac, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4e29529a2086773d78badf5969cbcc07a80cad2f35cc156b477e61a9c01a0985
- MakerPaymentSpent: ce1bb66abe043e93f2b0f4cc0e5002ea15889a4d867af9228824b5ce86e67ac5
6c3e02f1a1b30dbfde10356d0b888dccbbd74d89d647fbd1836869800259c708
Both payments are on their chains and locked to the same secret hash f4002d44d2df7c5cee7ffce390c8d685a2e979ac, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f14277d9135fe07884b090c658aa26d1614db3bc8f0f40faf019f235d7528fca
- TakerPaymentSent · TakerPaymentReceived: 6c3e02f1a1b30dbfde10356d0b888dccbbd74d89d647fbd1836869800259c708
- TakerPaymentSpent: bbf2d01e7cf2cfaaaaf1f8ec8f80e65a91500b8d72923c5e7ef9e4663627bbfa
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.