why1 reason
spend_windowspend_window_exceeded
this would take GB5QG674O7TSWPGNFGQVKNJNJ6RERFA3ITTVIA4H5YW4F7CL254LCALT to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- cf73c46d805166eff48e675e037c9770109a1cb3a93a999a3a943411d5ac73ba
- request
- 2f69c505ded7ea6a8e0b87b0442f0c6e1868ee6307dbcaa80307ed3c9092438f
- transaction
- 5fb24c697d77b9042cc2b99e9f7f79912588cd82cd5b61e41a60cc415e46a64dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56858
the chainentry 56858
- sealed to the entry before
- d06238bb1ccbff558d4a8323f0461dcee9bc4dd94070d607975c4b61384c4662
- this leaf
- b478149120441565067a264929e1c4b5919e433e65b6abe38e6399e8c8ec36bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DOSbxgVoYaIHOFaIM6d/FeIp7NqqLuaOSw6cKbtoH5hVyonRZ9oj4vjdj4eLzsh0XAM7KzkUEaZ5djN4YIr2CQ==