why1 reason
spend_windowspend_window_exceeded
this would take GD5EMRPMBO37GQUC6H6IOQGNZX3CUXBCNONU7FTXQIJC7IYVKWTO3K3L to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a0e2c2b0a77a56489d9ef8412c24b58fd964de74bdf16b68452397185145993b
- request
- 37169a1851af229a86f0cb32360e8e14089b983e5c4be0d939ea3a843693b17b
- transaction
- dbd1231a13644865ed99533ac34c1a0f7884e47b5647a9f9811e7fc5cedb2ee4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62919
the chainentry 62919
- sealed to the entry before
- c9881837ad1a7dfd900219fe3426fe7e13d177ce533e30fd6dfac67df013f2b1
- this leaf
- ff8f5022b65b149b29a7db962df8bb90b2e7adf14b745bcd7fcfcea2a3db69bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eDPp7SufAyPokDOIGJJFfk0QoXJwn+jwU6ag53akUdTbKgbW7xbJt8dO94Lp0nky+J4xXtbSuYwRY0rdZEcdAg==