why2 reasons
spend_windowspend_window_exceeded
this would take GDWF6SKYXVRFCELNF7EIFY7NYAVDPTSQLJL4B7EFHKW4CUNDY7VVFP2W 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
- 1447a96c7c970d4641f07e8b70ebf41cb8448363e6ab58d3056ec1fbe83eaed8
- request
- 504e4eb2354d8bf0470bffc1929c74391d26cdcd9616219663e5ab5f11a364f1
- transaction
- 4fac01ac2a38842e104f1b1bf933ff8f1fcff84f719178aa46b1f45f442ab36fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31461
the chainentry 31461
- sealed to the entry before
- 703a272d73db1cbf0c7cbe8cf25e2fe741b4b8ce55152adfc9b64b2fca6d951f
- this leaf
- fd7450923a3f29c3e3dfc8eb27d7cb392cdd487012cb53f214ec9ed2edbd48ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K+9ZC9YFk5cB/lJasuTa4tbrwTofVol2tvqYMOFnUGDHGLPkaLgNxXgHPgME9keOkNR1NYQsPtItCRM2Z46WBA==