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.
8e81ede3fdfa838f18f7b1f0cf224192ef680fe4ed9b2a9ed93ed29eae4eb4e3
Both payments are on their chains and locked to the same secret hash f87e2ca3e3c6fff1ae5a57fa0116614fde8f6125, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8e81ede3fdfa838f18f7b1f0cf224192ef680fe4ed9b2a9ed93ed29eae4eb4e3
- MakerPaymentSpent: f6b65909c11c64c5b91b4e43554f0bad5a88ed6f091e9e22ecebc50d886d10b5
354f494f528bbc36f59b548e7a37b8694fbc00ed63933c20db7a49ff6d51306b
Both payments are on their chains and locked to the same secret hash f87e2ca3e3c6fff1ae5a57fa0116614fde8f6125, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 848c33d0ecc5b06f119007ce41336e1c857ddc387047af0ead80e58f16c16451
- TakerPaymentSent · TakerPaymentReceived: 354f494f528bbc36f59b548e7a37b8694fbc00ed63933c20db7a49ff6d51306b
- TakerPaymentSpent: 9a8f8c7d5c6f8b6f3c08e3b7529ca0f6ca3be2e51188dc08f67c1e95aedb7395
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.