why1 reason
spend_windowspend_window_exceeded
this would take GDNXKSW6HJORCVTV3DA5XB4OY3E42DVMQSHLBQFFZYINTSGQONUXDFIX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f0e884238b8bf0ce4f9ddfdcca4cce8008db19805ee756f9668ed7d3efbef585
- request
- be0d3ce0f6f6108c3cc633b7b1cfdfd6b3000867ba987d5589fcdec12c35f2da
- transaction
- bf3bc6fa4e62c888f4f183d3536ad42d2a3cd273faafe3bb7b70c08818e5665ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31795
the chainentry 31795
- sealed to the entry before
- 8c7047dfeefd071d9b569c40b4f3e61e7cd754f3d3dd58a8f3a4a45ec8c9fd52
- this leaf
- 363810e192ad5e5293383ffb126f263bef4087568a3bf1c01bb55e8be7fbada5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TwCeomQ1MLhLQnnO73suTmcsZkZP85qGb7Xu+4rX9G6cVUfJi/h+WqRlE/z4S7lyngZDS4AA09wQvxG5bWRfBg==