why1 reason
spend_windowspend_window_exceeded
this would take GBYL5SJ4IT4JBFG57VFRB5SFZLND4EOCQCMFRZBAPTESN75R5L7R5TQZ to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- c2e88d6619b0fc33a0b4a7dec01fcd1407618cd49bfcac3a4f2319be5640dc40
- request
- 765e67fd92d0722805e5af4634b542cb6571b113df7cce5a718c9a9497a893d3
- transaction
- 69c9d668538bd1446b6db8fd4775af6d8a87d11fa253019b9889c937bba52e60computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16614
the chainentry 16614
- sealed to the entry before
- e235eb95cbbaf689327b51b7fef6dae0e8a3d50403311075848041ea35425767
- this leaf
- b72ed4d5ed00c5cf2a3aabb2bba7ca0ba53ff7dc0b0cd97a912fcde9963b1e64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cpio6HJBUhfHysZLEbXqjzGrLlLCDBZ4ofgI55ms3LKKxK9qBGJUiYVQX1R9dXZC6cf/sg7qpgkLMiHOIFtUBQ==