← previous blocknext block →recent activity
Analyzing
Block #105,619,046
33 transactions · 31 stateful · 2026-09-17 13:37:12 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,619,046 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w29w310w411w512w613w216w317w421w530w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a58d502…385c
0x34b655…2a6f
14 touches
21 conflicts
0x73d1c723…3e1d
0x34b655…2a6f
12 touches
15 conflicts
0xf06fce24…887d
0x34b655…2a6f
10 touches
10 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x29239774…a788
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 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 0x2a58d5029f…32385c
Audit this contract →
← previous block·next block →recent activity