← previous blocknext block →recent activity
Analyzing
Block #76,090,287
14 transactions · 11 stateful · 2026-05-21 17:31:40 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,287 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x9560013d…8caf
0x91b81b…6d56
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0x9c8d6dd6…d61b
0xea1b8e…c5ec
4 touches
1 conflict
0x9c8d6dd6…d61d
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e473
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e474
0xea1b8e…c5ec
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: LeverUp: LeverUp
1 conflict on slot 0xbc33a9294a…c28b24
Audit this contract →
← previous block·next block →recent activity