← previous blocknext block →recent activity
Analyzing
Block #106,906,601
25 transactions · 24 stateful · 2026-09-22 01:40:57 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,906,601 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w17w28w39w412w113w214w315w416w519w420w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xa06430bf…57ce
0x34b655…2a6f
10 touches
10 conflicts
0xf2ed177c…74be
0x34b655…2a6f
6 touches
3 conflicts
0xf4b03cbe…2840
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x10f63e18…4bad
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
15 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity