why2 reasons
mandatedestination_not_allowed
op 0 pays GDSH5KKR6QCOG6PHR33SD4CB5WCLQLKQTUDP35V6WBU2EYC2KPPWBGXS, which is not in the allowlist
counterpartycounterparty_denied
GDSH5KKR6QCOG6PHR33SD4CB5WCLQLKQTUDP35V6WBU2EYC2KPPWBGXS 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
- 2374efcc5635bb738100dc425b912fbe89fd129301c313ecee69b914f5931832
- request
- c972f39539ccce113e1daeb6b855258d5f4d4e0adbbe8ff5289e13f0deb19af3
- transaction
- 644adc61c960e87e2464d9fb63bf6a7c40e17b62ae298d18f7d4ef07cfb7fdd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51629
the chainentry 51629
- sealed to the entry before
- 83616ec14cbe56ffb4303bf3d769cd18d1506ed7eccd32263703ee077594e189
- this leaf
- 9db63d729a28e60d5218c6bb14e9c81ea30a17b6388963df1263037e9dc0a917
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- btZEmmaTMMqxweYsRLtqzYKnUYufKH1SK1ssU2UQO8nhmWizKGCBRY5vslp2wwZ/qNaSAiNbbA1WC6V6tccVCA==