why1 reason
spend_windowspend_window_exceeded
this would take GBQXHUU2IC4C5IGZ6DLEHEX2XD6N6MZYB6LTVEBVFTHSDAYBTMSP4BHB to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8bc7432780ed7c1d4db03bfcb72968cb52f598b056a59e6d46f2853210dee72e
- request
- dfc4c4fc347e140ebab0255581f30bb8cc904d3b928496ad0ccd9be303278997
- transaction
- 8fd2e90f266a57c2572ee0061892213c9879620b10d6d98317c2ae8bc9cc6917computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42660
the chainentry 42660
- sealed to the entry before
- 43bd1b78aacb6e4adb97580cbd5e2ab9544bad964d480382ba4379de49a24b78
- this leaf
- 7936be529f69d9c9b6cffc0b4c362abe787a4931e645b1882df5e14bb8a35ddb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- niVvsUzWwoLZUdX/fgtMRZPa8K0JUCI7IqhmWLYXAaNPMtMLqoGastZOH9k407IlmwixnqFfuXFMDeIySPynAg==