← previous blocknext block →recent activity
Analyzing
Block #96,274,482
18 transactions · 16 stateful · 2026-08-15 18:25:22 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,274,482 · 18 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
1w02w13w26w110w011w112w013w214w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0919e62…a2a8
0x34b655…2a6f
8 touches
6 conflicts
0x92d4e9d1…b273
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6c67b60d…ed32
0xd32edf…ff58
5 touches
3 conflicts
0x4bc1b6fd…ce27
0x34b655…2a6f
4 touches
1 conflict
0x52fafa24…6bfa
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
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 0xd0919e626f…7ea2a8
Audit this contract →
← previous block·next block →recent activity