← previous blocknext block →recent activity
Analyzing
Block #96,836,035
109 transactions · 108 stateful · 2026-08-17 17:30:02 UTC
Parallelism
95/100
Blocked
4%
Avg conflicts / tx
0.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,836,035 · 109 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2105w3108w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x092b7171…c16d
0x34b655…2a6f
6 touches
3 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfc0ff691…88ad
0x34b655…2a6f
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x42e917f7…ed8c
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 0x092b7171a3…96c16d
Audit this contract →
← previous block·next block →recent activity