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.
467b615c8907580e901a3201c153170d1cd9d00eeba97fdbd8199faa8af4b00f
Both payments are on their chains and locked to the same secret hash eb8546f46eff6f55fa602a5fd6b107414f86cafa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 467b615c8907580e901a3201c153170d1cd9d00eeba97fdbd8199faa8af4b00f
- MakerPaymentSpent: ea2a2d1b1bd16292e47ec6defa9000d0aaaa3a869992be582b95153af644d6da
030e5f299669b08589a82350a18bf14b2b943c8247e70fa12484ff6fdedfa4ac
Both payments are on their chains and locked to the same secret hash eb8546f46eff6f55fa602a5fd6b107414f86cafa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b59fc1f1892d3266771dfbf86a8ddd08edc320871e631788f4d4c419cc0090ff
- TakerPaymentSent · TakerPaymentReceived: 030e5f299669b08589a82350a18bf14b2b943c8247e70fa12484ff6fdedfa4ac
- TakerPaymentSpent: 18c36ce8fc93fdb8b4cfeb3ad4d016ea1ea8b65cb32f95b8d29c2f534f575401
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.