why2 reasons
mandatedestination_not_allowed
op 0 pays GAZZHMTXU5Y7DJIUWSC7U7L4ZOHOO3VJ5O2B2WSWEGSSYQCPAIGTIQ4X, which is not in the allowlist
counterpartycounterparty_denied
GAZZHMTXU5Y7DJIUWSC7U7L4ZOHOO3VJ5O2B2WSWEGSSYQCPAIGTIQ4X 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
- 879f0d4ebfc9e3ba4595a4dbd044e0749cf6a0b4d91c96b1c06cc0e17dac6890
- request
- 04704f7f0cb0b355740c2021d80026b1ef4dd03383070099c5574996c6d985d9
- transaction
- 00665ce0cb094651ee16d3cdcfe6663d2684a605e7d9a743b65cc4c5c37f391acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21234
the chainentry 21234
- sealed to the entry before
- c481152fdeb154ba2f1b86539cb1f0995e0824b098879678600dd44a4b535d8c
- this leaf
- 8521da3767a4a491bbd82a2f4d5a00ead279f5eb4c88b0e382d88c8dde905c68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fw2IsfUu5bIy0X2neM+Zs2I/08aB3VwTlD5YvOnkMWs4m7Tek/vPmpbuaGVqLfRNfImuCHnPbaz45oHqxGhEDw==