why2 reasons
mandatedestination_not_allowed
op 0 pays GDMXLO4SXOALK3BIDOPEVFRFUECN2NTR4FQUDNLXPZ6LI3G2JHCYKLP2, which is not in the allowlist
counterpartycounterparty_denied
GDMXLO4SXOALK3BIDOPEVFRFUECN2NTR4FQUDNLXPZ6LI3G2JHCYKLP2 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
- 0364268f0f7bcab46e9e3cd6aa757bd6211a7fdbf58b28615845b267b2f37501
- request
- e830d8487c702c5f8664e47998329c27b932408ed17a5eb10507efa368113b24
- transaction
- cc6297f4621f8c6d2c2f8345c610f3f9a29cade6f201b471a415bf964b7c433ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71207
the chainentry 71207
- sealed to the entry before
- 352169f00e5595cea9414ec7767a23f81ab5f75ebcf6f4623cea4c902f424683
- this leaf
- 010da8c7aa7d7619625246fa2a58e23e2dd9d732e6b5bba2f2d0a411c3b3a295
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zi052pwSLtNara6RniLRVfLxMebpzUB4J6ycDAQuf1XHbr3SY3kMxlSQ3OC9DGRWif7khk1hSaa19KARk4o1Aw==