why2 reasons
mandatedestination_not_allowed
op 0 pays GCS5A6DWSFTUZMC7VHTX4Y7J7CM7G3U3KZRNOCCHHFRLMTD7WNTCBU3I, which is not in the allowlist
counterpartycounterparty_denied
GCS5A6DWSFTUZMC7VHTX4Y7J7CM7G3U3KZRNOCCHHFRLMTD7WNTCBU3I 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
- 427c96e34db75d824a1ed6561175eaacd20b992043627adc44eb9a8863e5b674
- request
- 9da861cac8eff0eead577dc2b2230004245177336ee0068f72cd02a7bdd8025f
- transaction
- dcc16e72ddbfe33a6811c60f8d5fd847d46182635aaadf4b4c02a5bf56648068computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13082
the chainentry 13082
- sealed to the entry before
- 1442be8e75a6bc8342711adc2f8434cfab1a9cf01cadab26d06d4deb41e31969
- this leaf
- dae147bd61c9bb2853ab736e2970b84762d3cae887d5fd698fff7969c2fb822e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2Cce962IfILQ2KQRS0miwLCDBGERyQNyceHKNVS7WrZLEOEbqOW7wJMzrkgyzPQNhbmfbQmbOQRCjfCz2zJNCw==