← previous blocknext block →recent activity
Analyzing
Block #106,477,306
19 transactions · 19 stateful · 2026-09-20 13:39:17 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,477,306 · 19 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
1w02w13w24w35w46w57w08w113w414w015w216w517w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0xe32e848a…851e
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0x52723002…65de
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x525bf8cd…bd48
0x34b655…2a6f
6 touches
3 conflicts
0x6d955786…1327
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
15 conflicts on slot 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity