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.
a0ac70b3f57ad0ccce7895052af716f675d791f53ce8d6aa276d0b5582f8228a
Both payments are on their chains and locked to the same secret hash f2d310088808a86b0317fcb1a14fc35a0ecc7d87, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: a0ac70b3f57ad0ccce7895052af716f675d791f53ce8d6aa276d0b5582f8228a
- MakerPaymentSpent: ba99756d4d45d6143129c6e6f7ad8acd1fc6c7643e5cf13e4c3f002d50746c1a
c0c4beff5ed099996a1d4d5779ab5dd88f42053cb375ac1a07755e57ac8e6bc3
Both payments are on their chains and locked to the same secret hash f2d310088808a86b0317fcb1a14fc35a0ecc7d87, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3eebff608dff7157f48ffacd65cd3431aacc393f5e1a8099db52fa27fc3468e0
- TakerPaymentSent · TakerPaymentReceived: c0c4beff5ed099996a1d4d5779ab5dd88f42053cb375ac1a07755e57ac8e6bc3
- TakerPaymentSpent: 351ac80b0f952e716de87f1176e46c78473569037426f7e7b1b68f7369fb02b2
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.