← previous blocknext block →recent activity
Analyzing
Block #102,382,159
29 transactions · 27 stateful · 2026-09-06 05:08:40 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.66
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,382,159 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w310w311w012w118w219w320w421w522w623w726w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbba00f17…d5ff
0x34b655…2a6f
14 touches
21 conflicts
0xbbc4bdf7…c62f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x987859be…2686
0x34b655…2a6f
8 touches
6 conflicts
0x9bff3222…a246
0x34b655…2a6f
8 touches
6 conflicts
0x9c088939…ddd7
0x34b655…2a6f
8 touches
6 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xbba00f17bd…bed5ff
Audit this contract →
← previous block·next block →recent activity