why2 reasons
mandatedestination_not_allowed
op 0 pays GDMGW5MOWVLDHAZRFOYEJNXE56EX2LBNAU6DVOVCLESL2SGQWX3X435B, which is not in the allowlist
counterpartycounterparty_denied
GDMGW5MOWVLDHAZRFOYEJNXE56EX2LBNAU6DVOVCLESL2SGQWX3X435B 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
- b23048f28dabb5d9f3e03361d4616d954da55bfe68dc52696d5b80c9d2b9c25b
- request
- e7f8623898c3d81b713372e876a1cf04ff564045c5ddd762e70d20dcdad0ecb3
- transaction
- 3c43dc1acba2b4abdd6b8540d6d05ba2c9b0111d060dbe56c120076b602c75c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34822
the chainentry 34822
- sealed to the entry before
- 488131b48a77d7d4e7cb57d0b35794492b1b08664efd1451d0bf6c31e68de24d
- this leaf
- 0a57118715a72acd9708e46dc9ee3eaa1a56fd635147ef91262dbcf23984b492
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sc1XI58J9QIpyBMNF4uAfUu6B7M7P+B3bnYUiQdOOQzUi9Be7zWdD8Qt9pNBQ9rk6BYQJ2PZJQElX4sFcfiGAQ==