why2 reasons
mandatedestination_not_allowed
op 0 pays GDLN3CJVZHXKG5WMDMMSTOVIIC3IJFO7J6AEFWKWIC42ARX4ZZYBDD57, which is not in the allowlist
counterpartycounterparty_denied
GDLN3CJVZHXKG5WMDMMSTOVIIC3IJFO7J6AEFWKWIC42ARX4ZZYBDD57 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
- 659fc440e4e412b6c09b9a39af1eab4fdc9b8ae1a487a066f5638ff9dbee1bcd
- request
- fc91b9b5ebab4a44a6ab9819fa104abd21d1673f30453134c9309b788b791f7b
- transaction
- da2adfe0a34b0bf0372484562171f0c455081fe01e7e009bfab25eacaa787027computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58869
the chainentry 58869
- sealed to the entry before
- f28f728b52f79fc2883527e9d1498693f1e61509023ae72e21bdddc11a838066
- this leaf
- d4bbc2f7f7e26f5fffdccc5a813eb1b5ad2c33942e2e182468564c8ef524b743
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2Ee1yfxGEJdVMQJjcOdF4OOeX/uNeb2a0+QTqCscZIivR5zaW3fE8w2eVUv3Tu56yFuj3X3oy9AT+UZYSeeRBQ==