← previous blocknext block →recent activity
Analyzing
Block #106,394,728
31 transactions · 30 stateful · 2026-09-20 06:43:39 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,394,728 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w09w112w213w314w417w518w619w121w222w723w824w930w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422bab7d…0f6c
0x34b655…2a6f
14 touches
21 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
14 touches
21 conflicts
0x10ab11a4…d530
0x34b655…2a6f
14 touches
21 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7cd9fd28…a158
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
21 conflicts on slot 0x422bab7ddb…360f6c
Audit this contract →
← previous block·next block →recent activity