why1 reason
spend_windowspend_window_exceeded
this would take GDAKYCCT2ZUJAUDXFH6A5UQW3NPLPFHZUIVASLHRXJCFY4A7CUXPGEJT to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- d9e6095125585900720242e802165db1b40838bb4a8ef20c6d682e7988b71860
- request
- 4e391d4f7dea74b937ecbabd574cc2b144900f1f1cab8c168291319ee5d740aa
- transaction
- 392e63d27496139be9f4db9c70a230b2406b54ad3d8e67f8ed85e4a624a2d74ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48249
the chainentry 48249
- sealed to the entry before
- 7db4d9a104319f02324ca608ee7bc838e292c22ac947d63bbb881e8fd661b02f
- this leaf
- 60a55ea1dfa5f601a6a0b96397f448b248f568d0db0756d47ae6ee51f57fd138
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ssYr92lbbk3iZmBNEammiLbjIt9j7/r17qrPG7kgLrcZWidaNLEMuAazejVwoSUMtdatIfUmxiUgbGIeLWHDDg==