← previous blocknext block →recent activity
Analyzing
Block #96,639,265
18 transactions · 17 stateful · 2026-08-17 01:00:21 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,639,265 · 18 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
1w05w06w17w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb07f01e3…0ad4
0x34b655…2a6f
6 touches
3 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1d372d00…8884
0x34b655…2a6f
4 touches
1 conflict
0x4e559ae1…82f1
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
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 0xb07f01e333…f40ad4
Audit this contract →
← previous block·next block →recent activity