why2 reasons
mandatedestination_not_allowed
op 0 pays GBSSJHSG5EYW5FI6GH5DAOABXZ37DUH5N7IICVH23DQIBSRHBYIFKEKJ, which is not in the allowlist
counterpartycounterparty_denied
GBSSJHSG5EYW5FI6GH5DAOABXZ37DUH5N7IICVH23DQIBSRHBYIFKEKJ 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
- a7bc5ffd81eacdbe9cbe0c186357d20f70dd2149c52547ba40ec410b93514422
- request
- 67e5c0ae45066da4adb53eae93e45d0329a562c18d473e4c8fb82396145c28ed
- transaction
- 50b24e92129a203fea663e1a684fde7a625d16ce6ad5e35f91ac975b3133435acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58622
the chainentry 58622
- sealed to the entry before
- 105dd4754c2184aebe0adacc1951cbb353455c732008c71cc6e0f973f1c02b33
- this leaf
- 9d5d39f5200b7a447e10b3017722e3ac4e8eab2fafeb4e918bb67c843b0cb144
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I8HS6Vf3vNMX1+4tY81UFfzLDLrv4+IyrQUYNQl6s58loaz3DjAlX9eXyOSBlm/71bsOgNNlgI55CcDLV/ddBQ==