why2 reasons
mandatedestination_not_allowed
op 0 pays GAYFXEAB7W7IXDBFCJCDPWGQRQCE7ZSZDLEXSLEYWIGCIOZDAFDUWPG3, which is not in the allowlist
counterpartycounterparty_denied
GAYFXEAB7W7IXDBFCJCDPWGQRQCE7ZSZDLEXSLEYWIGCIOZDAFDUWPG3 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
- 043d994fe5afdc9d56c6eff9bc0fe1a4d9f049f25eea901a411a2c9882846ed3
- request
- c0b9d2d6e33a6a403eba0da5a39917c2a97577275bd5a4d6e9cde493f335b783
- transaction
- e1bb422afbbfc535eaa316acd1a992c262e865b47f478182198c48da89912f33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59108
the chainentry 59108
- sealed to the entry before
- fd06ac91c2dde789c446560535341b3ce8d8795c0cd0fffc4b524ff8745508f0
- this leaf
- ff936fcdd6894cce997c61036862971577f9a7fa8f98b21b0bfb6a6b2ea9ab46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4lhgHYJybOWvyEZIW2WEZ3pNKqnHODQMhI9x7C77IgnLPYUy+mb4CH9GWZAC/xdedQFvZGofJQD5s5zlIU8nBQ==