← previous blocknext block →recent activity
Analyzing
Block #106,422,329
19 transactions · 18 stateful · 2026-09-20 09:02:33 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,422,329 · 19 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
1w06w17w211w312w413w514w515w618w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63b3705…28bc
0x34b655…2a6f
14 touches
21 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x2014e4bd…c10b
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 0xe63b3705df…7328bc
Audit this contract →
← previous block·next block →recent activity