why2 reasons
mandatedestination_not_allowed
op 0 pays GDEIHUMC73AQRBLMU5GZBGFTSBK5N55KU636OZ4I4KLTFS5ECPCA63QK, which is not in the allowlist
counterpartycounterparty_denied
GDEIHUMC73AQRBLMU5GZBGFTSBK5N55KU636OZ4I4KLTFS5ECPCA63QK 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
- 3655efb8ff6963079060587bb1430796d67672710ae7dc9500757c63b5271a2f
- request
- 5bcbae4954d4c9852541f76dc8d89dae8a5cd03dd5b8e8e895d67bb515576a2c
- transaction
- 32c3f57d996356781c6b7eb78c33dc33ea8abd6d4028c80e01112297342e747dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69047
the chainentry 69047
- sealed to the entry before
- 584f6cd3bce139bd8dc07453c1c21840e780d7fa31f0bed9852901074b690c44
- this leaf
- 15ad736377f177d971f4dedb159555995f0ab12f97300e9c56b42ec7a6e8ffc5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tWCsQMYAnFQseu5MtupVgNyKDehIGIr9RGhzXOQfGQldaW1JaPVnwHg1ivw7COOJRTCfGvZ9aUyx616KwbriAQ==