← previous blocknext block →recent activity
Analyzing
Block #102,802,207
18 transactions · 17 stateful · 2026-09-07 16:34:05 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,802,207 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w110w211w013w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbc38fce…2d01
0x34b655…2a6f
6 touches
3 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0xf1894e7f…30fe
0x34b655…2a6f
6 touches
3 conflicts
0x56828d99…6126
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
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 0xdbc38fceec…8e2d01
Audit this contract →
← previous block·next block →recent activity