← previous blocknext block →recent activity
Analyzing
Block #96,373,977
14 transactions · 8 stateful · 2026-08-16 02:45:46 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,373,977 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9eaa844…2344
0x34b655…2a6f
6 touches
3 conflicts
0x32790195…b240
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x3f4f9f22…8ad6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57528477…786d
0x34b655…2a6f
4 touches
1 conflict
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xc9eaa84497…802344
Audit this contract →
← previous block·next block →recent activity