← previous blocknext block →recent activity
Analyzing
Block #106,458,260
38 transactions · 31 stateful · 2026-09-20 12:03:27 UTC
Parallelism
53/100
Blocked
74%
Avg conflicts / tx
3.11
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,458,260 · 38 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
1w02w13w24w05w17w312w413w514w615w716w818w919w1020w1122w1123w1324w1426w1632w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
12 touches
15 conflicts
0xe1944aff…428b
0x34b655…2a6f
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
10 touches
10 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