why2 reasons
mandatedestination_not_allowed
op 0 pays GDBAOP2NSJHO3CJCKLLB7GZIQH277C23PPWRUY4UQMLLFJONH6CIDU6E, which is not in the allowlist
counterpartycounterparty_denied
GDBAOP2NSJHO3CJCKLLB7GZIQH277C23PPWRUY4UQMLLFJONH6CIDU6E 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
- 88e76e64780489d1eb79cb29a9d8f68ca541c17b63e8b66b74ca3840b052e844
- request
- 7337ba33afaba46acdf2f7a56868ae300509996f4af7a04578ef301c3ae007ba
- transaction
- 580a3b0213514e1f2784fb23a8747eccdb234d50701ae51a70b46d8160d30130computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11228
the chainentry 11228
- sealed to the entry before
- 45f671a508b2df35ee43f03b29b799d4730f9d28ab9a98d96d63aa00d3f0dcc7
- this leaf
- 57b3b58a21703c8352f9f82ee767a2655b3bb05e2134659d76674001efbc2765
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- joX8a+bzpUSVKPTXG9lcDSsPOefGISON8awFDS0QIY2BHWwreUQMOzEPrkK6j56dGDsIoRNUUabl9nrFzfecCw==