why2 reasons
mandatedestination_not_allowed
op 0 pays GDPPSK4ERVKKC46RHDZZBPRG4HEB32DZSX3IVCWEXRYFGVWCFF3RZTYW, which is not in the allowlist
counterpartycounterparty_denied
GDPPSK4ERVKKC46RHDZZBPRG4HEB32DZSX3IVCWEXRYFGVWCFF3RZTYW 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
- 5bd358f11267fab8f2396257fa8345ccb1f198b6f2bccbdaf2299fbd0933a0be
- request
- 727408ffa37da9598e03a8e73a6393e3c9cd2e9585ceb8b3f29149ef01aa751e
- transaction
- 745ec3444e2a96f2d1f1ba0326eefb537b49e3b935300f86baf004ef08b7aea1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30523
the chainentry 30523
- sealed to the entry before
- a9cbb35d5a96036ad632231620f6581e749f84481ec46fced49869cafbc26e60
- this leaf
- f7ad74932d450171637336267bacdc90ac319eeee4d28ed51d31ec9f6d1d2f0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H1OMITIJ3kAhSn9mgjyWhFaFbAJyNfECWuY1VHStbYwb6u95WINBOICOKIXBSmYDL8aUel4G4DZxxRUNjtVXDA==