why1 reason
spend_windowspend_window_exceeded
this would take GDZ5JVY6VUOWWK7E4L4QN7WL3WXJLKL5AP25WRZ2QNJZ7KCLESPQR5J2 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b197065f0cc4c10cf2e5173ce3258c4bab09a84314788d3e5f420adaf3be109b
- request
- 2c06b56acaea837bdb32adb9a25304c292a9c424cb02fbb5633885aaeaa5c7a1
- transaction
- 8e9a493738252d1b818dddb52b6137c28ab31e77bee335ac047270dba1369cadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8444
the chainentry 8444
- sealed to the entry before
- 2a0cf56d093c46a0e5e7d17839e8f1644b64e9e461de294819cfaf0859519a60
- this leaf
- 6b3b3048fafcabb1a49ec254a27c75d50df4b0c681060f399de02bf4129b88a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LJ0ScfAsSpBueYCk2/VcbKuNSpVWZUZMpqfVnJkf3B83Uw0BkI8/hkc3IkPZy/GO1Z+sN+g7pTfzPLaKp5M2AA==