why2 reasons
mandatedestination_not_allowed
op 0 pays GDNDOOFO5XTWMSRXK3RYNEFJ2R3SXWMXO7N7SRP7MGEFE5VJOR5YMD7D, which is not in the allowlist
counterpartycounterparty_denied
GDNDOOFO5XTWMSRXK3RYNEFJ2R3SXWMXO7N7SRP7MGEFE5VJOR5YMD7D 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
- dab6feb6904786992dd5fe6bd748a03e26ed38c5629d28ef1dc515cd3b0abcdc
- request
- cebabbfed54cbdaa823fd4c67e47a0f2d47aa35c1f44c00eca192209258a0689
- transaction
- 0b0c02fa9bf1c413016cbaf0824c41279901df0173c56e346d88abaebaa4087ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64622
the chainentry 64622
- sealed to the entry before
- a1c240f8dcf7d31ef8122056fae08d936475bf5643fa302bb49e1191b7c4042f
- this leaf
- 14f07fac001d1c00086104356390c889d7092a864de93df4f71f9b9e6b17b558
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1/Gg/g1IaJ0bs+BiTZwTZXujprKyqso2qg0wACIybY7EEjPcJ9GMi9Ww2X1RVKeo6K1ow3VMrm14+1fzfvhMBA==