why2 reasons
mandatedestination_not_allowed
op 0 pays GD5OQRYHXNVVQGPRPPSCWN56LB47O6F7DH326UPWR3WJ5OQL6ATH6CBQ, which is not in the allowlist
counterpartycounterparty_denied
GD5OQRYHXNVVQGPRPPSCWN56LB47O6F7DH326UPWR3WJ5OQL6ATH6CBQ 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
- dd941f60fef9a0aaa15652a7b966ef4081c58d328cd34a441ecff03bea0df6f9
- request
- f4507c5c18a33d35cc577d1c99e52daa76045ce6d7e1ba11b25f684173f1e868
- transaction
- 33867a75a14e1605298a7e438eeb9b5c57b11900b0f3fa68d46a1331119ffbafcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35482
the chainentry 35482
- sealed to the entry before
- 55a9bf90f30cf24e655300ac8d70f3316018151a56ab8af7e90613bca3d0a1b7
- this leaf
- f04d5c7530a2e7744b70ea08a741c46e0c00a28a9f66aa42c4307d1df258fe4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jjrxeinYm6u5wgnpHrWCxcWCkunxyKYrnx16PaJZSg9yA0QpXpvR7mU6Nh2Y5B1ar3sOoPWWbwOC3xfCs02RBQ==