why1 reason
spend_windowspend_window_exceeded
this would take GDNZ3FBDQCVJ7YN47NT5OA6PYVWH734L24NNZ6P7U3LK3S3OUWBZCMVR to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- dd7d50c57c5be8bef12e18b479832fcd4bc0b70f069d3d9ad03a6e2923b77404
- request
- e82cd294f005b506b36f5f1766ffd3e37511e85f8833f6c48dd3be438a20ef49
- transaction
- 2c83c44d740b8c8ded48aded50619d48cce6d7fed125d35a84aa9077b1d9c8c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27473
the chainentry 27473
- sealed to the entry before
- a222f5b7e988952656336fb3763cfb36bd72953148946e94b7de4a2c62e9a4cd
- this leaf
- 5bc61d5c42ac203ff97fdc5a7a6ee129301cc0df33479953aab7500254ae5991
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZXm3dFWOKGyOdxrE66za7VQ1tuxQ0A/hbBWPJCiGeKGsNlkno9TW43tyJHMzDvWKeF7XUdS0LZA/PO8kTSIDDQ==