why1 reason
spend_windowspend_window_exceeded
this would take GDVME3CZ7QROXWC6XKZREU4Z6MOR6LQPRWOZ6AAPILXF4NE6RQL6YXAA to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- fee2e04e33bc92d33764df55e7f858272c18b06e2066f4fae63c58987c85f629
- request
- 31d7dfd5e1d8a5024f381cae02985b5093b8a6874be43cb421067ddb5c52ab86
- transaction
- c0b6da36d446fe4421104fb28c169d0122e72f03193fdb409cd84fdad206efd2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75433
the chainentry 75433
- sealed to the entry before
- 3536314092bf1e844ec4188dc9b0b91734cdbc4874c455946386c51c5385acd8
- this leaf
- a09c0d0d011c2dbf251108a09c2695b3e8569d61cd1acff91903aac2c56757a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6wr45xejDGeehYyLjHWpePxqWY2OX127A9ti6ein5xNh8RMurv4Cl7V7FyMd447Ki3RRRug5S63mZMwM+SohBA==