why1 reason
spend_windowspend_window_exceeded
this would take GDWXJGP4ICZLCSOMJCD23KZWXCJTB5USO7JP7ZH6C4GIXDSR4CCX6WC6 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ea0554590dd0eabdf68d70b9f3bce4e9ca930eeda523d1ade695b896e98944f0
- request
- 7311ad8ca482591c3badbe3c0fc23f8a6b3561560d419def7dee59d6d03a5d87
- transaction
- 4b4aa37a0df44eff35f3faf8222c66799c1a2b5c48d4102a6668351c922d4349computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18133
the chainentry 18133
- sealed to the entry before
- 4237ca29e7beea29c99bf5fdc0e85b4edeec4bb611ddbb9f74ef10d1b58cc5bd
- this leaf
- a3c989f444bac51bade221fe68ed01f2b53647b62b84ca2003dbe616f662beab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- joKt3QGyeUe6jUcTvJSbu+7qERTToLCAneodts5+DYnz4WzPLCb9tQIeJ4E0xk35HQDf36RoeuaCGDw3abr2Cw==