why2 reasons
spend_windowspend_window_exceeded
this would take GBSDE7H6AXIICVLTM4KVG3NRBDTONX7OC2FRM7Q6XDQCH5PQZ4W3UWHM 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
- 19e5a94bd7783609fed6e009d92d66273587ad2eebc251bf0424a84a5298c50f
- request
- 2f938b547cf344e88c7574c37b8e5b191eec48a1f592c7ca235df73657708fc0
- transaction
- 9b85f86a505bec1744845f9676cc18e6129170861c81269a47193ed91e048ea9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71800
the chainentry 71800
- sealed to the entry before
- 19f68d6dbee074d611b4e5f95ae5ac8d5bb19ff5f8d03d6b09f0b4fe51a297f6
- this leaf
- b30bbf23919d81e104de51c0f58c0533fff8ff3dc96467ccb09660e82aef438c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N5PHJY0KFbdN90GiG6Dy+w6mp9m+qNAenT3OaPfj7CkuWx4c9g/2vU2S01echfKwTScaNnN94lCsN6TDkFxGAw==