why2 reasons
mandatedestination_not_allowed
op 0 pays GB5WUX2YQZE6ORKI4XROKY4JKXPEYCPTAYBHON6T6TWWQUI6AM64336E, which is not in the allowlist
counterpartycounterparty_denied
GB5WUX2YQZE6ORKI4XROKY4JKXPEYCPTAYBHON6T6TWWQUI6AM64336E 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
- 7bbcc2607062e3d9fb9fe8398220720546b779675c7245d472915b73dd20c85d
- request
- 8457553414a83911b81d46e8f3b035e4d50f990437b36d0529b79252d255ae79
- transaction
- 9cbbd5ec80c3cf82c682b9f9d7fc2e3aaf0cc2bbf4c1d90950ca26b3e9449b11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37037
the chainentry 37037
- sealed to the entry before
- b79d81b0ba249348434e9886129c6afe39acbafaa4101fd99271018525cbb35f
- this leaf
- dd40601cd91c3d56c9c506a4d64a40634d70ba442fa8251dd57383cb30b42814
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P2R+klkVTWFYUO3PZhiVRNNr5n0nPVk/xxhV7IjjdCB3xb3XpvbveIkPD86Z1ODluoAjq1HYItO6Ciujs6r1Ag==