why2 reasons
spend_windowspend_window_exceeded
this would take GDQ7ORDNO7LHMT2BK7FTJ6JGULN6JV2QXMTLQRLNFCICY7RTZZ6CRI4Z 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
- 80458a6fc248b61598e4989bb19f9dc65d3f0d4d50e0f9b7e66c376a6b069386
- request
- 76698ae6e8b9da68afece59d5c96705098fd4b7c538d2fe6ef52a7f4a21415db
- transaction
- 8f4604e38092849c005c7bc5cb8aebce6dac77ecf9a611e98b2fe5990a436ae8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74502
the chainentry 74502
- sealed to the entry before
- 3a0c6cd5684ea669d55c3ef13cf119b3aac3a911332f1dfe73e1d2f091bed210
- this leaf
- 5a419ace41645659f3704c154ce4fd975f002beac3d3bda0a035bc8ee96bda93
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VLu79LYlkWJprH7wj1zi5Sfup/yTZLAGnsfIGk+MMO9XlGcVyMSRqy8zvw+MlwqDRh4lz6vIwbjz6uhPsrKtAw==