why1 reason
spend_windowspend_window_exceeded
this would take GCAISLE7OJBW32I2M6A2FQHXQENK3SDPMXXUM7GGPZWI3DH2OXKHX3OX to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 85d99fec9cbb6251467c77f0e94ae01e639730940e73c9af45f57bd5f68428b0
- request
- 2bcab07e6524ef9629bd75811ddd6bda0abd6bdf3fb6aa9642b6e53f4e8ba47c
- transaction
- 8dfeb6d1c405c9aca6fed1ac034d538643a8676cedd789235156c9e25e79cc68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62630
the chainentry 62630
- sealed to the entry before
- fb7b096bffc7e91a4f120a3a4189118feee4c7a608e2a92c8ffa07dbc6301f51
- this leaf
- b804250a1fc2c773c1e6f11b45d3fd3807b3ed7ed9707d9f9bdc028d3d45bb2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v42rAaDqgMPINSnp4LuhKJ+vxAG8UuS0wujibpsSVZBevLe/0PGJnX9n0C+h/aemEaHo3Au+AmVeZJbVWoA/AA==