← previous blocknext block →recent activity
Analyzing
Block #106,366,984
30 transactions · 30 stateful · 2026-09-20 04:24:01 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,366,984 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w19w210w311w418w522w623w624w726w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb46c7ade…d4b0
0x34b655…2a6f
16 touches
28 conflicts
0x5fa29461…492c
0x34b655…2a6f
12 touches
15 conflicts
0x5d1ac445…5233
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8d664414…3344
0x34b655…2a6f
10 touches
10 conflicts
0xd25997d0…a685
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2c2761c0…476e
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
28 conflicts on slot 0xb46c7ade7f…44d4b0
Audit this contract →
← previous block·next block →recent activity