← previous blocknext block →recent activity
Analyzing
Block #106,420,223
21 transactions · 18 stateful · 2026-09-20 08:51:57 UTC
Parallelism
62/100
Blocked
39%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,420,223 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w111w213w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb77c2d1…a699
0x34b655…2a6f
16 touches
28 conflicts
0xebf19faa…72cb
0x34b655…2a6f
14 touches
21 conflicts
0x051ecd30…f7e7
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xfb1d5846…56af
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
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
28 conflicts on slot 0xbb77c2d115…09a699
Audit this contract →
← previous block·next block →recent activity