why1 reason
spend_windowspend_window_exceeded
this would take GBQEGM75NH4HG6MNKAN4OJ2ZRYL4UTSIFSCFVEGGIUT46F6EQZ2NI5I4 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 631e8e1b3cfcfa57eb388e7bf94f1f45a5cc53e1182fe9351da42645c9790ffb
- request
- 8fe249f698f4e828e5b14aa506553910673cb3310e72daa05359814db6791750
- transaction
- bb074379db459ea4c827091332bd55631eaf080a6bc74094ff33a6e96f89c40acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22209
the chainentry 22209
- sealed to the entry before
- d9f4bb7f86ce51f375648cb31d544bfcd2df0e3e7ed9ed5a8a8427eb94efba9a
- this leaf
- b95cb22c909a0bbe546f43bff07604462c77b76239d57e74768a01d27f7ca752
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b4rbcEvQYUmbdlANXXCnW1yKRyXEhCmLSOhzljPlSP1PlQU1J0Q+qjx4htXNfBvl7wTKhMzGYecF17XrQvXuDg==