why2 reasons
mandatedestination_not_allowed
op 0 pays GDS3J7A5ODYVWV6BTWTXNHTDYBN3NUYJKLF5X2EKIHXSYPWSW6MZQ2NR, which is not in the allowlist
counterpartycounterparty_denied
GDS3J7A5ODYVWV6BTWTXNHTDYBN3NUYJKLF5X2EKIHXSYPWSW6MZQ2NR 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
- a96a64cf4d9045f2c4c86729e424add4c1ff2d3c556f2f91d5c9e0cd403f2b01
- request
- c52843a2a67aac2f9e087479c6d0574599b131cfd887feee53abca9f1f3cd9cc
- transaction
- 03d4ab5ef4fd11448b75026a80dd0fcbb0219bc01decc12e40b549c7e927318ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 617
the chainentry 617
- sealed to the entry before
- 88e85e6d89f1939c5709377e04c406a9737a9fa1e30d3a9ad2aec07923ad8997
- this leaf
- ac39d02786abaf91bec81c04f0cdb64d505be188c28b885646fd57bcf38a437e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- shjzJ6rXO7RfxVfG+gFhmKfeVEtjIhtlzaMfL0Vf5Ze4mSZqhEdBbwc96iTY5d4BVTCuUyCUv3rJKTzC8ByYAg==