why2 reasons
mandatedestination_not_allowed
op 0 pays GB6HD5X3YC3XZO3QSZOMAB3BTMO7NDEN6FRWT5JL5DLENUIZZNTFLUGD, which is not in the allowlist
counterpartycounterparty_denied
GB6HD5X3YC3XZO3QSZOMAB3BTMO7NDEN6FRWT5JL5DLENUIZZNTFLUGD 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
- be92d23e5115731b0d16251511b3fb65525219a7bbb95eaabe8dc106ef066c26
- request
- 48340d11d1788f1d5f7ad38678a3ee3c28b07fcf3b8035f075033afda024bfba
- transaction
- b2f337deed77815497a41f7b165d2564de89d1597e44ce7acd25999519a133fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30918
the chainentry 30918
- sealed to the entry before
- 44f76ed72b7cb3f4ddeac78a91d9da9581ea6e7d37fc4b3f314a936d38546511
- this leaf
- 68ce2e42cca036b49322d28c03881a0c887632874b46e418ee12c332d0860e40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- caL8swKv5yjR0gxJ7DrXOTbemYWowfbIdOS1eONerpPI4HgsPGK5Fwxo6oQCVCNu9SpitdLu7zpNvOA8wbY3BQ==