why1 reason
spend_windowspend_window_exceeded
this would take GD47SGECRN2EU2URK3TQF3R75H6ZND4WEQT27PHY4GRLLVCXJSHTEBI6 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- d421eca58508342e5c577da4360dbc317fb68580d6559ca6b0f58f353866be43
- request
- 91da5c85e87771d321d77533238a5a58b577dd4dec61a7622459ad0b4b0e30b1
- transaction
- c7144efef43b2365c424602f5371ebc35fb1075df89bc9769ff16f1efc518c6dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51190
the chainentry 51190
- sealed to the entry before
- 9b5359e514a51e763b3a6570c242c73d755aedfaba273159bd998941f8ed8690
- this leaf
- 7765a1816e506b960cbb78761ad23717d3218c26c58b5306d7d2377b27ca7844
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UArp4++rA6A9q7ZawI3v3NgpZCIXsqpVyHN1hd6jmC8F8HEFqLloGHuyzITSHcBVXvsJD8eA2+MJW7egThDLAg==