← previous blocknext block →recent activity
Analyzing
Block #106,422,719
33 transactions · 31 stateful · 2026-09-20 09:04:30 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.97
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,422,719 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w317w420w521w622w624w325w426w528w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf0fd5d…0c8b
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
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
36 conflicts on slot 0xedf0fd5d3e…320c8b
Audit this contract →
← previous block·next block →recent activity