why2 reasons
mandatedestination_not_allowed
op 0 pays GDSUVGJMRLVLQYYX5ZLGFQHZPB5VXTDCITHDDTE4PXWQ6RSAS36PD3XX, which is not in the allowlist
counterpartycounterparty_denied
GDSUVGJMRLVLQYYX5ZLGFQHZPB5VXTDCITHDDTE4PXWQ6RSAS36PD3XX 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
- 4c886f50cea5e83fd806f5a6206dc3e0a899610814e601f2adcd17477779cca4
- request
- 26a38d1749b0f65e5f08cc003dcf76a2312cea2bae603ff65d65a63b0986cd4a
- transaction
- 083c4d7b2a56100c6b12810933dc3657d0cd3533ac442250b55ca3c5ecd020e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35167
the chainentry 35167
- sealed to the entry before
- ec5b17018f5b0e4c73ea8c3f70564558d86c4b7e53fdbad46e3462934d86b733
- this leaf
- 6af8de7d3e5f107f5c6ea788c1935e8cce09566158a500a5d2c54044abc68744
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YUX27r7cNO1LIWG+0sKdeeeifitklKlnMvlETUHYZQuUhI1R5Fpe1/49qcdwoMhw25qrXuvX1yZyc7+JWaFrDQ==