why2 reasons
mandatedestination_not_allowed
op 0 pays GALTUV3ZJQ5W5HMKP2DXOAN6RDLCBRCSTGAIDNQAS33P4CZA6JJY4CYW, which is not in the allowlist
counterpartycounterparty_denied
GALTUV3ZJQ5W5HMKP2DXOAN6RDLCBRCSTGAIDNQAS33P4CZA6JJY4CYW 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
- c15c603a1b94a278b8e9265a5b03ba0004c4f179940594244efb62322f1f33cc
- request
- cd55ef6b9576eec607631ef0dbc94740cb422072d85451dcdd28be2c3b46bb22
- transaction
- b6a96dd5ee01d7b3180646b79f43c096f93ee68370a667afadb3ea702780170bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24682
the chainentry 24682
- sealed to the entry before
- 2cca597668f55a9123182c43f6072c1b8a551be8e623e2758bb75fae5416cd8c
- this leaf
- 9521ee3ab5dd2c936ef9f00ac2f8dffcca9989ff0b30f8e745197d3d1ae49104
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /vFtwKHlhE23MGxh8EUy7zYgilBs6RTCRv2kTQDKsMcKwkFNtI9lGA0dz3bJcDlP7x9K4lf9JdkeubFe5aDyCw==