why2 reasons
mandatedestination_not_allowed
op 0 pays GD2DILMJA7I7O6IEZPGFB4LLDTALXISPS5VPZJIVTJBH3DN34FTH5C2M, which is not in the allowlist
counterpartycounterparty_denied
GD2DILMJA7I7O6IEZPGFB4LLDTALXISPS5VPZJIVTJBH3DN34FTH5C2M 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
- 320c8b3f16f7a4ce3375dc98bf7c2d099e505766b23f1807e73091698503a554
- request
- 9af5ae09daac820c10574ac341abf1515c60b62cc0a77c46a7d4ea6b8e403543
- transaction
- e5ea67a9990a524a135a28e86e257927513e3ab55c21af82ee651fb0ae8d0ce5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12685
the chainentry 12685
- sealed to the entry before
- 61e2dc9bc771d3d87a6654efab213d6652e124e2ced527c23a933e7c87f6e888
- this leaf
- b9e248801085a6872c0c11480580e832d40fec595872397c806a131c13f93ad8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7LIn6y55OtXPJM8gJAGDy7RxU3WTTdI98d0/oRY6+MOxoLtdAZ6XHmULgYCZJ/FUn2P5Dhe5MVUsh7t3gXR6Aw==