← previous blocknext block →recent activity
Analyzing
Block #105,856,178
23 transactions · 21 stateful · 2026-09-18 09:32:10 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,856,178 · 23 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
2w07w011w112w113w214w315w416w517w618w721w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0xb9315d69…267b
0x34b655…2a6f
8 touches
6 conflicts
0xc0ded688…b825
0x34b655…2a6f
6 touches
3 conflicts
0xe2247875…3173
0x34b655…2a6f
6 touches
3 conflicts
0x97e4c862…4419
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity