← previous blocknext block →recent activity
Analyzing
Block #106,801,106
26 transactions · 24 stateful · 2026-09-21 16:49:58 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,801,106 · 26 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
1w04w19w210w011w114w315w416w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9edb7ad7…8d56
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xc454c0e3…02ed
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xdd2800d9…7d27
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
6 touches
3 conflicts
0x15a3656a…60f2
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 0x9edb7ad7f2…288d56
Audit this contract →
← previous block·next block →recent activity