why2 reasons
mandatedestination_not_allowed
op 0 pays GD6XXZC5GBJ3N2GHAF5ZZEHFCEFUVRXSOZCRSJLCQUM6F7HLIFR2XM3P, which is not in the allowlist
counterpartycounterparty_denied
GD6XXZC5GBJ3N2GHAF5ZZEHFCEFUVRXSOZCRSJLCQUM6F7HLIFR2XM3P is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- ceffd1e2c8acd0f10cb4801500c1190e3029d1c8867ea9a5ca4fda2f0d03ba99
- request
- 073ecef8139e965fe6882333ca14973e0c444df02780bdbec42e2c73ef284191
- transaction
- a7b59e262c98e84fc63b4af510620db95d00be5e04e0580e8917d78fa012c4fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11698
the chainentry 11698
- sealed to the entry before
- 7ae18a17a15f76e983d954f7959b8491f7db473cf4a66c6f3ce1c1e0f4e07e87
- this leaf
- 951e46a7a0036b18f51bdf2862f85a3ab0b8184ca2edf744cdfb7d9e2960d9b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fCKRU0ixbYBiLXyEdq667ZDGxDNF5l1vr4yTj84mvAJ6jQJCDmTLxudx0japhDbd1/W1dJvsaj+BWbGp3IpdDQ==