← previous blocknext block →recent activity
Analyzing
Block #105,850,654
18 transactions · 18 stateful · 2026-09-18 09:04:21 UTC
Parallelism
61/100
Blocked
39%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,850,654 · 18 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
1w04w18w29w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf6b6a764…04cc
0x34b655…2a6f
12 touches
15 conflicts
0x2827ae77…4368
0x34b655…2a6f
12 touches
15 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x11d7cd2f…553a
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity