why2 reasons
spend_windowspend_window_exceeded
this would take GDRCDZX67HHKXY5TJ23IS7F3VVQY5Z5M3LQB6UYGK6CAQVJS5YWVDG6H to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- cdd344fe352fd00e7cf25419006ad2b5b28ea3ce721ec63105878e02dd7e4012
- request
- bbd60a72359e1e8057e78cb80c5ef1d7ce7110f798c332ce2d0f0bcbd3e0651d
- transaction
- b80eac9c3c1605cf81b127513ca255bc74cdc1bdced9e8b622a981a1c195a151computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30982
the chainentry 30982
- sealed to the entry before
- 8b40f5b1aa60a6185103c9eff1e827d1d587efcf0b75102998ccdf7065a2542b
- this leaf
- a0fca06fd5658ceb72af7c5cd35e8609202cec4d9fffbc7fbb401f8cd970cf35
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c2rvGZdZHVY6XDH88d30xLA09lpfdzikJM49FXILwTx5oJU7rgCKMd+hL2wwgaXk+/gNoIuB4k0he3SQK/0lCg==