← previous blocknext block →recent activity
Analyzing
Block #105,608,843
24 transactions · 23 stateful · 2026-09-17 12:45:50 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,608,843 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w19w010w112w113w216w217w318w419w320w521w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c6c7007…e8f7
0x34b655…2a6f
12 touches
15 conflicts
0x1e737223…2278
0x34b655…2a6f
10 touches
10 conflicts
0x28a8cc9b…db4c
0x34b655…2a6f
8 touches
6 conflicts
0xfc2493d3…6898
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x0c6c700718…0ee8f7
Audit this contract →
← previous block·next block →recent activity