why2 reasons
mandatedestination_not_allowed
op 0 pays GBZUHYV5MBJJ7ENSHJ47PH2BGS2TZ5HNRHDRS5X46OOYJKHY5B3FTMD3, which is not in the allowlist
counterpartycounterparty_denied
GBZUHYV5MBJJ7ENSHJ47PH2BGS2TZ5HNRHDRS5X46OOYJKHY5B3FTMD3 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
- a88c0ca42b35fd73beee3fb239ecb32edbdc5f2f4eb56330c15a3f114e3039d3
- request
- c888bcb63a95959333578caf04b9c99838685722fe7aab3b80280794e9da8ca1
- transaction
- 495372832861e41a99b692f50abf5fb74e686265ff480ca90a033e30d37d083ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61392
the chainentry 61392
- sealed to the entry before
- 3883fdc293dffb82190393d0193a28aaa374df74656c221a2814bce4065d4fe2
- this leaf
- 0d9dbcb812875f45abbd5ed2d82a98ded527ecf0838d0ef4942da1b7770fa104
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 92UoTwwOgmmpwbFJM60UhejpkMFYhngJLcM+4xJlyGBCoM6u6IrgqOOMbkuwBsWmx91oFivwaHIMf45raPJXDA==