why1 reason
spend_windowspend_window_exceeded
this would take GDKRHEYYBXK4FKNQDIRTLHESIF2PSA77P3PQHHV7COZB2A5RS5UWZXCG to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- aad73d5ee06732c7fcb30b9aae25bc70c2cf7245c45054edb2756c1e0016a495
- request
- bb7800023b865681e70a816f1cc9e74cbbda67d527bb3a2e8acd1c03ff5bdbec
- transaction
- 5745d65742463d88b79bf96b612e419e2b2959ad7f499bcaff9a25d3a22609e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6529
the chainentry 6529
- sealed to the entry before
- 2068aa2c4a7bf5c18cde188c16c77f2f3104fb2e242832361b310778f12e700b
- this leaf
- e2a9d98bfa1064bdb5280e1e5d91761cd0a51dafeac6a64963f7ffe1e634b995
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TxAXbFCWvmspBGxgHsRcPTvMhh7phxxBxLs8TMCUIQrOqsXJ+t5b2TQh8rHtKHx7Ym7hiL8x13k47OvTMwS+Aw==