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.
adba280a02e41062e459e2e40a715f2d269c8cf27b205a9abcc6365f663a2c15
Both payments are on their chains and locked to the same secret hash 1c4ee18a8026960389fec660bec5ad6f9fd97f29, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: adba280a02e41062e459e2e40a715f2d269c8cf27b205a9abcc6365f663a2c15
- MakerPaymentSpent: aa7b468bcdbbdcc7bf1a8279e59bbf467f863525ffa3e14eef476ea42c08756b
3c939bbd34409e60b5428938f19ac6c319801e9c783b11340278f14b15942dd0
Both payments are on their chains and locked to the same secret hash 1c4ee18a8026960389fec660bec5ad6f9fd97f29, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1541df666062f1ef6019e0ac64ad83b097a4b679dff12ae2ef7d21ce69f1138b
- TakerPaymentSent · TakerPaymentReceived: 3c939bbd34409e60b5428938f19ac6c319801e9c783b11340278f14b15942dd0
- TakerPaymentSpent: 2167406294de061ffa60ee635daa8a444f52f1092248e08afd2a6de8b858535b
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.