why2 reasons
mandatedestination_not_allowed
op 0 pays GD32ZGBM26KJSQQ5MDF6CIFOYY4MJA4V4ZVPL22N2RQI4W2XIXQFEVZ6, which is not in the allowlist
counterpartycounterparty_denied
GD32ZGBM26KJSQQ5MDF6CIFOYY4MJA4V4ZVPL22N2RQI4W2XIXQFEVZ6 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
- f932be75b6d5a1837ad6b4d6e1e4f3331ba6dbdec3d8a1055b19cd74b9e0940c
- request
- 7f6e10596a2832f1fa1106a537f25a6e4714478732591e3af21119cf2a0d2ca8
- transaction
- 62a0fa48909671e8825b92bdae2f87b2fafadfba22efdb9d7ec8e8d1ec02cd1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24276
the chainentry 24276
- sealed to the entry before
- a309a1a4deeefb32938982cbc6a7853c80dea1feafdd49241b7ef28c77e1a8b3
- this leaf
- c37a0afc9116b4053ef0a921f70414d5b66110e5f72c775efe64a09178106200
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X7Wz0JZ+lVVH/ga6HrEfUBNM7ZdVku/hJTVJHGx292/GsFvL8PQ1XaO/4n8nODquOCnppKDQ2stmkzHBkksUBQ==