why2 reasons
mandatedestination_not_allowed
op 0 pays GD5A35O7AOTKZSD3WJOX2DG2FLFUPBX7W7GE4KGJY5NR53BLWP6QYWXR, which is not in the allowlist
counterpartycounterparty_denied
GD5A35O7AOTKZSD3WJOX2DG2FLFUPBX7W7GE4KGJY5NR53BLWP6QYWXR 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
- 42603f5853d4ea9d0a4dc1fd3325faaa73240af5301007094d4f0dd9bfd6932c
- request
- f758550106456ea1a45f419b7038368c08eb1f47d005af90b3c8efeec1f3315a
- transaction
- 17c2651c7a556b04c25346e0dc48215c084cbc7139cdcc68c71042b59666e5c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22706
the chainentry 22706
- sealed to the entry before
- 0d6055c23df6bd3ef223d80817909d6a166a99b7e0b79ba30a5efd14c8e84e90
- this leaf
- 323cc005624a491c211c5180135b3dd7d67c56c98970e69708ef41f51532cc32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GrVkdeXHI6oU/DsmuX8H4zACPDjlnwvdFqMfnieMRboK6YwusixLx7QgxP5nLhJZYVLf0p15Kk+UU4xmsAaVAA==