← previous blocknext block →recent activity
Analyzing
Block #96,592,716
14 transactions · 14 stateful · 2026-08-16 21:06:14 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,592,716 · 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
1w02w03w15w06w17w09w210w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0xd64c1971…1bf2
0x34b655…2a6f
6 touches
3 conflicts
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x32442ae9…5e78
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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
6 conflicts on slot 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity