why2 reasons
mandatedestination_not_allowed
op 0 pays GD6XX32FBL5EUWGVECQVABCA4QSFFBGJBPUY7AMCVMPYNYFUWOIGFRAO, which is not in the allowlist
counterpartycounterparty_denied
GD6XX32FBL5EUWGVECQVABCA4QSFFBGJBPUY7AMCVMPYNYFUWOIGFRAO 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
- da65b2109c32657d20fbf87989033e70d19ff6b740ef1e7b3635bc0ed4771f87
- request
- a01f888de2b3ae9d5a0beb89bff58f369a6c0b865aed9afdc5e2c045452e8e88
- transaction
- 7ac6407723151ecd3578c0f0bc3d84c9ccc7db6b0d31c7c9fbbbba3dc4e4fbf8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53064
the chainentry 53064
- sealed to the entry before
- 6689cd2c89bd034359251a05e1b812ecc04206a7931f239015fc4a176d5761b3
- this leaf
- e50f2ac90ad0014d57fbb8f6a2d59421c36a74530a87fdd1dcf8225ac74ab9e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QR8Z5DJZroBqnZvTzs8i6i5Q2QfWdm2H3jk/HLGKaX4KLexuvfQ33Ff60M6EaS5OhOSlsHFiMRtL8taAGDLYBA==