why2 reasons
mandatedestination_not_allowed
op 0 pays GAJIW5FYRX3ABDIJXMLHEQB7N2HMQWEECCE4IFHW64E74KAUOBLL7XEU, which is not in the allowlist
counterpartycounterparty_denied
GAJIW5FYRX3ABDIJXMLHEQB7N2HMQWEECCE4IFHW64E74KAUOBLL7XEU 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
- 923f1afb0cf884c1ff2fe9e92cf7e16a4d93a02d45f58d40b92acfb4fa0a708b
- request
- 3fdf2299227581eb8052ddd718aec8b27acec8b86aa37734ade29bfb06b95735
- transaction
- 6fabdddb17af837cde850d4e37897f8d07235a420f36a15cdfbec109f7c16afccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72180
the chainentry 72180
- sealed to the entry before
- 9c48e4b2cf45d9b5a77bc9dda289e5b6c270ad82783d26e55774f7854c0bf8c2
- this leaf
- 8cfb787124eb2e6f1bc39a09a2225390c3972c245b87523906dd3df3b8daaed0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 99Yh2MsQ/dKy7ajWVdoK92mZaSHMkDuqWZXRHN9lZPyYWIgp0neEylkJZghf6mBzqh0HLhoP4Vv+KXMv10ofBw==