← previous blocknext block →recent activity
Analyzing
Block #106,328,542
33 transactions · 30 stateful · 2026-09-20 01:10:33 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.36
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,328,542 · 33 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
1w03w04w15w26w37w18w09w110w211w312w417w119w423w526w627w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xd4f40644…e33a
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0xb654bd89…a83b
0x34b655…2a6f
8 touches
6 conflicts
0x3018a378…d7bb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity