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.
afbe743bd91bd1e644ac532ec3817115d3089a790c0b3852174a54ca85e25d44
Both payments are on their chains and locked to the same secret hash 70ad3bc15e59470c6fcb141863e3872f751794e8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: afbe743bd91bd1e644ac532ec3817115d3089a790c0b3852174a54ca85e25d44
- MakerPaymentSpent: 4bc77ce78fa5a45a163900c5e6ce3c3198e495fd83d490e5a84e97f55cb19e93
96e348174585c410fdf1e8931bb5e09e5f556490a06e882b43f72440e795a56e
Both payments are on their chains and locked to the same secret hash 70ad3bc15e59470c6fcb141863e3872f751794e8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b9133980107dd7446a7f027a261cc8ccb3454437ff03617d333aa74eb715fb65
- TakerPaymentSent · TakerPaymentReceived: 96e348174585c410fdf1e8931bb5e09e5f556490a06e882b43f72440e795a56e
- TakerPaymentSpent: d790353ed0d85c8712f6c8c1d5e01148e230eeebd61eda7a0307324b1c395a29
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.