why2 reasons
mandatedestination_not_allowed
op 0 pays GDPITDO2RX2VZBENAMJW5Y2GDIQHFXUBYAPJ5FIHRKVVVNVMHKKEG5MZ, which is not in the allowlist
counterpartycounterparty_denied
GDPITDO2RX2VZBENAMJW5Y2GDIQHFXUBYAPJ5FIHRKVVVNVMHKKEG5MZ 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
- bfd193c38da7c30861077a93e56680c8874e796b8d0b572bbfa02aa7bccd12f5
- request
- e7ec541540b80fda45de0d28d8e53e41ceba25d1608026be588f25f43d2fa236
- transaction
- c4b37f26ae37840457fc3bb2bee5ad6643a250cdcfdf2db7821b17c8e8a22e9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43521
the chainentry 43521
- sealed to the entry before
- e805201f9cc4cb657bd7c8e73d6b6ccc8f96d2290a91a6783be6958081b74741
- this leaf
- 919ed8f2fd811fac97e78e54a2b3eec333d534d5448bc0ecf55fe0c501ad3e3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xAZYA5+DyOe7kzJLEa/+x9dYmUykfzjPf1apC/vjdewksRCJTJ34lkxKfMQpySJlBvsP9FAO/eYeXSf9epoIDA==