why2 reasons
mandatedestination_not_allowed
op 0 pays GBOFKQYN3ZUA2REJT67PTDINGHHLQYXF3ZKKRV7YXXB5ZVWUTAKAPVWA, which is not in the allowlist
counterpartycounterparty_denied
GBOFKQYN3ZUA2REJT67PTDINGHHLQYXF3ZKKRV7YXXB5ZVWUTAKAPVWA 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
- 5abde800941c4368ae5b4729e1c43c5826b1e3310356f4179eae90dd7d081a8a
- request
- 2815be89168b25763c6844633feaf3c282bed284e905fcab2f49c7a654756bab
- transaction
- 98fdd88bf70462202b2846915658c7cb373a54486e7c6e716d96523b63a3de3bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8248
the chainentry 8248
- sealed to the entry before
- aca60b916600e83f1d194db892390ce8dc198e947950188b7c5fa28c9487b28e
- this leaf
- 710b021a23eeb0b2abd3279b021188436b84f7caf4631f89518d5122633e9d0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8rMB/eE9BVnKcbeZABJw1Hbwl4YIFlrzH/d7edh79qBJMqGzsD2QiPJTNnmlm+6PL9XqlnShd/DQGPQsnCgFCw==