why2 reasons
mandatedestination_not_allowed
op 0 pays GDQ6TWF2FKKSY2QUTCF34SN2QXKFIWHY43WAUVGZPEYA7ZI6ZYBQMX2E, which is not in the allowlist
counterpartycounterparty_denied
GDQ6TWF2FKKSY2QUTCF34SN2QXKFIWHY43WAUVGZPEYA7ZI6ZYBQMX2E 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
- cf500a82a4b0962680f712d9a7fd305d695ade1b3ac2533b724cc2bf74f1e575
- request
- 812117ad90ae6c7edd78bdfec8c55f894b2d35ad0abe903032eee3ad7d4aa1f3
- transaction
- f130e8cead86c1518a49da4fd5877970fcf08fd9e3604f9629176e8ccdfa241acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23190
the chainentry 23190
- sealed to the entry before
- 3e48560ee6299dc29553cba732f90698769ec40bbd1a0adce8eb9d35ef9b3783
- this leaf
- d2470c202c4f77347815166e3e8f741ec62951091ebf2d2d27ac69bbc46b844b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qAEKsc3JBepheQT28a1y2Y84pLj8raA3fWpeGBmgA+LC3FK3+5TV+G+sDsfzTZtVjbJqCdhForb75Q1lg9k1Bw==