why2 reasons
mandatedestination_not_allowed
op 0 pays GB73DXA5RHIEZVTIKQBKJ64HF72OXO224MXNIQKE6WOYUC5IOMQ6J7J2, which is not in the allowlist
counterpartycounterparty_denied
GB73DXA5RHIEZVTIKQBKJ64HF72OXO224MXNIQKE6WOYUC5IOMQ6J7J2 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
- 089d3302fbc479161155fc9d1cd6b1504c70f5c6af0a8e6fe432b1b88f2e14d3
- request
- 4dad37091b9453f2c5de64cf0aab13858f9d306c8c154806d79ed3dcf652391e
- transaction
- 441905d9da25cb084bfc0af3316a447ff87f9aae887084c738424daf8ee72d1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2146
the chainentry 2146
- sealed to the entry before
- 0977e4ade11979c29493943864fa35906ffb1a5939fe3a65f5ce15de14e95b70
- this leaf
- 4164d60d3ee153075894b396c252712a15a38ff649b654f216e18e8ad54a5f65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- viDavgmaDWEunqM81cq9ImoxlJ47/h3QHXGL1r9tlBykiGharrmnjnJp9euOG3bv/i/vnKwPAm6QsdaEL3GuCQ==