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.
36a107744c533d99c565265e3536ef39acc8f0dfc5d1af593e61822470fa0580
Both payments are on their chains and locked to the same secret hash b67ced62830264548fa599da143218feefc6771a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36a107744c533d99c565265e3536ef39acc8f0dfc5d1af593e61822470fa0580
- MakerPaymentSpent: 761916f9d20cdd841fcb6f397198b056dca67ceec3e05a0c196ee7abae7eafb0
518e29ad31da9415aee96f110a38b52d68baaa41b7a2c08bf159822a3fa5a93d
Both payments are on their chains and locked to the same secret hash b67ced62830264548fa599da143218feefc6771a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d7735c684b844931bfc4037852721744545535eab1f3b6f21a62b27b25bc945b
- TakerPaymentSent · TakerPaymentReceived: 518e29ad31da9415aee96f110a38b52d68baaa41b7a2c08bf159822a3fa5a93d
- TakerPaymentSpent: 4733b7d848bb05e0ead79f9b4e6637e5251ce7e254bb5dd268e0179a3d900700
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.