← previous blocknext block →recent activity
Analyzing
Block #106,370,630
34 transactions · 34 stateful · 2026-09-20 04:42:22 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
2.5
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,370,630 · 34 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w514w515w622w724w825w926w1027w1128w1229w1330w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
22 touches
55 conflicts
0xa384061e…9f51
0x34b655…2a6f
20 touches
45 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
10 touches
10 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x110b04b5…81c0
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
55 conflicts on slot 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity