why2 reasons
mandatedestination_not_allowed
op 0 pays GDR5WPAKONRRWRQEXBOTNRUZKNSRKV6HQ2TU665IMLYEMHR3MAWIRIZC, which is not in the allowlist
counterpartycounterparty_denied
GDR5WPAKONRRWRQEXBOTNRUZKNSRKV6HQ2TU665IMLYEMHR3MAWIRIZC 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
- 806c247c1e66eb81340ecc88db193a91a58ec9c059b4f93d41643f21d3c17c76
- request
- 21d261501511de5253d42de9c755f69ff5cf162b5bfcb42f070e779f2856a1c7
- transaction
- 3e79b374fae0216803fd7df64d652ff4a3b5f324ecb8ba30ec2d5ed99c7f0623computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28881
the chainentry 28881
- sealed to the entry before
- 6119130a1c8e7da41f50f8589f99dc2c2a0db9589cc297b761ce9a3af5b8c526
- this leaf
- eb40343077a7c4ebb3cf744a44e101fdab5b271175bff6c109d363aec604bd11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KWVPUGL1kAjyvxEgufdaj9aSKKTepozrPAfUwrsajDAJM8+/kkZmF+dL5MC9OvmhscL8jvWZp9jbgJTqL3ZFDw==