why1 reason
spend_windowspend_window_exceeded
this would take GDU3JL6UEA6ON32PTQESIDKQHNEV2KHCOIAN7LHS53XBLSQ3ZCC54GNB to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 3ef360911b9e27d213b563aa9f6f546e74bd90bb98e18d8910911fdbae328bfa
- request
- 18021bfe05d5ed1b247dd42e9d3eca4145d9bbccff332ca838136709447837b5
- transaction
- 0292b065c020effce49cd74d48510dd38cd024d83d7e47bd6812cdc6b7c2076dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14030
the chainentry 14030
- sealed to the entry before
- b6f380ba9cd224e61975ca2a73156a930449487ef906738f8958afc568e98ec7
- this leaf
- 89491c56c51ce3e66e7cde206498440a8d8f03ef8bf1248bd8a40df00063935f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NMt1laSy1cJrBfPPEDhfd7HU5IkyglzoOyeYhAmTXVka0OOh1oNViEp7wrvct8nRZd2QLcR497GElf+i21hJAw==