why2 reasons
mandatedestination_not_allowed
op 0 pays GBGGZSLHIJ3FIL4SPZD7QYY5WIFQQEUSJNIUF4H425XZKSEY7UPBUF2L, which is not in the allowlist
counterpartycounterparty_denied
GBGGZSLHIJ3FIL4SPZD7QYY5WIFQQEUSJNIUF4H425XZKSEY7UPBUF2L 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
- 9fc1314c4895d118ab4d23b5e52b6974484a236bbe8539af37162bbe08a6e2b7
- request
- 02792d019abde51d1bd96659c44b169c84cfbb49850d2a5dd6d8ce159ca6cef4
- transaction
- 44ce28495c37265b089a530762472c18373414b1b14f189c4b46d03305fa791fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37070
the chainentry 37070
- sealed to the entry before
- 536f23d5eac8228cd2fc3751424b114c16c7460a66040cb88e519b6eb723509b
- this leaf
- 3224cb62845b3bb15985b28ece6993c7825b2a0e9c82d066ba48cc1859d8066b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hHw+5ozjnsnraA5BVfJ0OA5s7QUMSoxaA9k1HvhaB82mH+/pEQnMn4v4AHNWvv4MLgNxsd/5LMXh7bsMZ/m8Dw==