← previous blocknext block →recent activity
Analyzing
Block #106,200,202
49 transactions · 40 stateful · 2026-09-19 14:24:36 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.24
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,200,202 · 49 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w411w420w122w123w524w629w730w831w937w1441w142w147w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1564b2b…970b
0x34b655…2a6f
22 touches
55 conflicts
0x5717771c…45ed
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xf1564b2b45…85970b
Audit this contract →
← previous block·next block →recent activity