← previous blocknext block →recent activity
Analyzing
Block #106,567,980
24 transactions · 21 stateful · 2026-09-20 21:15:38 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,567,980 · 24 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
1w02w13w24w35w09w112w213w315w416w517w618w722w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678dc413…10a5
0x34b655…2a6f
14 touches
21 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x5b0227d5…1940
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 0x678dc413b6…4210a5
Audit this contract →
← previous block·next block →recent activity