why1 reason
spend_windowspend_window_exceeded
this would take GDBMWOQTWT3SQG4XSO64763WE5VIG5OW7LYNDOQLN4XTOTYOMW5XBVZK to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 19ef1d4513d421356e53fca5b3ee278173fa7a1564c5b01eb94721858fa5db5e
- request
- d05d40eb45e1cef79cfa0490d06bad48477d8e3628f3aa103054edece437b8d7
- transaction
- 3a4ce8376ac2be40dcceeb873e8af4ae1b4dde0c1ecbd2c3d83a0a057f97486fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64006
the chainentry 64006
- sealed to the entry before
- 8c1a5f7bfee35521e829f7b51bcfae5d6dfd399d2924b56c8dcd07346a0803f2
- this leaf
- c8e5f817844a1a7c563e7d976a383daa54e80cd2e094be4edea7481d8f0d0b39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PVEg2UF3KLngIDKhMAQZIYcjtYXCznjF32YoSEqCDC73wRLktSf5RLkgdNt/fYPn/Tf+36l9Ox7LvHlOQXTpDQ==