why2 reasons
mandatedestination_not_allowed
op 0 pays GDD5KE2TPBDVFI4UFQXZ2QKJXLU7L3GQ2VYUNV4KOAFZKA2YAIVWPXTQ, which is not in the allowlist
counterpartycounterparty_denied
GDD5KE2TPBDVFI4UFQXZ2QKJXLU7L3GQ2VYUNV4KOAFZKA2YAIVWPXTQ 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
- 5db7a26135fa9c46da07f90a5a20555badacdf49485ac051982993b0732744a9
- request
- fbb627db77914cbd0a079e32c7475963abd2bb50b613428b6203233b9f9070ae
- transaction
- 25b35274a0500fbe40418df202306ab5de0ee5c39de9832ae8708dd0df7db23dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9930
the chainentry 9930
- sealed to the entry before
- 70113d23b03ab3a157255852b0a14ef568a6ba1e4cade1745a9c58023f565048
- this leaf
- 60bbd6f8843e0dbc540f188f2feb5ec109ab7315a0541bb216037ec22a0ec418
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7azRfHqeS7C0CNEtl0WEdcUrnirFM1XwWY4jzje/xxmasfC4x0f/HN7ItLj8aESQF50yWtIMUD5fWTuZWOsEDg==