why2 reasons
mandatedestination_not_allowed
op 0 pays GDMF4XFGFYUSQKQ6CSUJK3MUHRVFVOBWKA2UHFS3SHFLRDGA7L7JXFDV, which is not in the allowlist
counterpartycounterparty_denied
GDMF4XFGFYUSQKQ6CSUJK3MUHRVFVOBWKA2UHFS3SHFLRDGA7L7JXFDV 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
- 73af5d9eb1610950d348407a372bd6bbcae5b3e0d9d9bfc939f00cb74d3440b6
- request
- cbdad0d2c1a293cb82b52f81bfa0713f386d04438df65603bcbba27f76ded82e
- transaction
- a2b65bfcdecde9b9abb2b054fcc464a9b1572e69ffc581aa2c537b8e8f0a2b44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70265
the chainentry 70265
- sealed to the entry before
- 9d64d88eed5c8eeb6bfa6bdaf73981da505ead46d33bbacca95355528e8ed4b8
- this leaf
- 5c1b03bee16761c24fd26f51aa65eae5a95fa829cbdc8b50672246e71e5c07cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0tfBSpC8fjFQZqnkRUmEbdC5Fuy4a5RSsZR4ewal2ksQxGdqi0riMNnkBwVqXhSbwpSzHx4KcB3p6EWTqa43Aw==