← previous blocknext block →recent activity
Analyzing
Block #106,567,605
53 transactions · 43 stateful · 2026-09-20 21:13:45 UTC
Parallelism
68/100
Blocked
81%
Avg conflicts / tx
2.81
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,567,605 · 53 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w07w18w29w318w420w521w624w125w229w330w331w132w433w534w435w237w638w740w941w1049w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76e87dc3…612b
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xefb236ca…f49b
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
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
36 conflicts on slot 0x76e87dc3a4…a9612b
Audit this contract →
← previous block·next block →recent activity