why2 reasons
mandatedestination_not_allowed
op 0 pays GDBDK3J7QSNETRUUBQBF3LKV54RVQOXBDDA23AKVHOHUGIAQA36FLS5A, which is not in the allowlist
counterpartycounterparty_denied
GDBDK3J7QSNETRUUBQBF3LKV54RVQOXBDDA23AKVHOHUGIAQA36FLS5A 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
- 52b25367450bac2ddd1a817c55fe687ef3fbbf73ac1ccfd7dcfc2c7646013ed7
- request
- e870c647c2f117785c837ca1861901fca3f266f554ee6d86821f2e7f41daec0d
- transaction
- 5d078a7c4110b2ac8b8b3585c161a7eac473d53c6637d73da6faf86f0725bdfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22736
the chainentry 22736
- sealed to the entry before
- c51c9beacb3e5c0dbe2f165103b0f66fdb6197060d081abc3938e161ab95c1f0
- this leaf
- b40f68fda545119e41d155d4e0ce6536ff10b46d3cfff4d6bb70d81bffa38746
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OBCHdtN3nbBXYTvW2bwOnRvE3BqlPcxr9m71mXThfGwkL9QEW/nX5XaqStDV4k3Js1u1ioMOixPWnXeDMM7YDQ==