why1 reason
spend_windowspend_window_exceeded
this would take GD46672GIBGDL4I7FDNAAMFYROOOHLCVPGFYVEN7WSBJWWY645O2KQBS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- e3202b517eb3c719230f8971704d4d4ce603c0ffa2d40eabd0361d1c05b30381
- request
- f8c19b88589195c86e2d9b9d4ad354fdc7a890ccf95ce192136517887facca9e
- transaction
- a382109af4e034b66eaecbe82670b770010d8640aa305fa37d6f2e8d3f75128fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63795
the chainentry 63795
- sealed to the entry before
- 171aaacde41fe7ccc91ee0b96673120ce987ea9a68af70b512bc8a24dd23e3eb
- this leaf
- 88402627aecd58a0a50bed9c056b6af09e78e72dd0e5e9e2448949e8ef0c9367
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F9WgAL/Q4tXgLCDR0F55pumO85w/14Bszy4hhQSPgACfzVuZBSv7wAwAIJ2O0KUqq7rgvaAYgTQEzy6efUckCQ==