why1 reason
spend_windowspend_window_exceeded
this would take GD432K7OK5HGMNY6FZCT36UHNBOCSL6CCXBGYRZQB5XZBW27N7PGJ6GS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 7e09e0741e4257d7eee0ed7a9d362304506f0c2cf8eadfed6c2210fe3344b57c
- request
- c53db3f455e42c5d1c95b75ac9ef968539de6686ddba23ea6b18e17556ee02d1
- transaction
- fedff0f51f67eb58cf30b87bedb5f4583c0ba6b21458fc055181e5b1d34bc7a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30215
the chainentry 30215
- sealed to the entry before
- 3162cde9a22d7b78315e679eaef1a8117e948ccce5b5dd30f018004774cbb001
- this leaf
- ca2ccd9129b7eb31edd55f3fd491a3dc4595cca45f2b99bc5c94c9066ab8f3c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IXdSZ1QJLV5JuYejJ/F7qC/wYpjkMYacjkcKa989HaOf8hX0NLGWLY6PC/0Y7tiXX9ZiUru9ihaA4wCkZkudCg==