why2 reasons
mandatedestination_not_allowed
op 0 pays GDUPBNIUXYM5EIZSUL2CJLFXCCAIU2ZMO3FVRJBDDLHRZ6VRMYB5ARUE, which is not in the allowlist
counterpartycounterparty_denied
GDUPBNIUXYM5EIZSUL2CJLFXCCAIU2ZMO3FVRJBDDLHRZ6VRMYB5ARUE 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
- c154e62b6aad45ae14634ea6d1c7e1b4970c6b7dd49c14589c7aafe46391b4f7
- request
- 4b44f062fdf4533a98bc647b53696a7014b9563a5fecf4d16bce9d79510c759e
- transaction
- ee74df639c17ef0be23b20fe750565461cd588caf587bc0bcfb20776159fc668computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10268
the chainentry 10268
- sealed to the entry before
- a9c655b359f5b20fb4aefe9a943c2eebd50aa4fd7e832b8e8ebd0b1f8621e946
- this leaf
- 3646511016f3e65ef9d7b99da934886283d9039b31d898edd5ecf620bb104247
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e6yw8gg0cz20/jyxiL9zVtlnZqUjboWGhEWKLM7o95WLVO5bP76ERux8mlhnhAydCu4z1hecalOdnUosLYNNAA==