← previous blocknext block →recent activity
Analyzing
Block #106,185,407
31 transactions · 30 stateful · 2026-09-19 13:10:08 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
3.06
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,185,407 · 31 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w211w112w213w315w420w521w622w723w824w925w1026w1127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x854ce402…932a
0x34b655…2a6f
16 touches
28 conflicts
0x51f1f20c…d9da
0x34b655…2a6f
14 touches
21 conflicts
0xd62f3741…b903
0x34b655…2a6f
12 touches
15 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity