why2 reasons
mandatedestination_not_allowed
op 0 pays GDZZUL3X3KPJ2KG3RUQ2TZ7IPQAU2HUITHKV2MY7D7N45FIJ3QHK63UN, which is not in the allowlist
counterpartycounterparty_denied
GDZZUL3X3KPJ2KG3RUQ2TZ7IPQAU2HUITHKV2MY7D7N45FIJ3QHK63UN 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
- 8455c24a9040d0453136e6800c87ae947d20d22d0fcc33efae3d3371b5c18311
- request
- 76a1e13abd62acafb69ffba5cfec71e62885b13a9f11246717b238d3de559292
- transaction
- 668a89fb4406e21c88a329e85da6c5f10c38910922c5b9e16f1717db4cae3d30computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39468
the chainentry 39468
- sealed to the entry before
- 94e1b9077cd8045780dae2de445d34700c84016ef68c8a5ef6363512259ef5c6
- this leaf
- bef3230a5673c0f76420bdd7f2f2f50e3529bfed725b36828f4c6e5d7d31dae7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pStatRbG8xbxGx1SRubsL6nx9mgdAMt2i+fein0ArNq5+acyiQ/3u7dUOE4uW3NYgE2Rmln9VhYBvvKpl5efDA==