why2 reasons
mandatedestination_not_allowed
op 0 pays GDK3APQLE5LQP7FF4C6IRZO72K6YMRQU3KE6J4KAX3ALYPY72O5WHKS3, which is not in the allowlist
counterpartycounterparty_denied
GDK3APQLE5LQP7FF4C6IRZO72K6YMRQU3KE6J4KAX3ALYPY72O5WHKS3 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
- 8b5abb492fd57b998d1cd61b6909e077cf6c41c1a7539502e840ee0d75bf3566
- request
- 78297b20a9e04a90b88d1c987972616b59958359e1d72ba57a3a48aed6150e84
- transaction
- 424c7a3326016fb495d774ed8fdbaafca52e42f44ed8c62c25ae7c10fe8ef391computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24086
the chainentry 24086
- sealed to the entry before
- c85931c37750f1cb287aecaa775903eec9e6245d0a1eb55b53c4e3411c8010df
- this leaf
- 60a518c37d928edad05d44604ae7e286e01b9f5b0e7f997505b39811f650b1d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QatJQXN9/D3vGVVJVZCSxwCfv+KJK0zpMTFCxIKuyYSy6aYl5oi10RWK6FydQA2Hw286gMHmJXokkb9AMH0NCw==