← previous blocknext block →recent activity
Analyzing
Block #106,567,336
39 transactions · 35 stateful · 2026-09-20 21:12:24 UTC
Parallelism
67/100
Blocked
66%
Avg conflicts / tx
2.44
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,567,336 · 39 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w210w215w117w218w322w326w427w528w629w730w831w932w1033w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefb236ca…f49b
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x429245f7…351a
0x34b655…2a6f
14 touches
21 conflicts
0x172b0de5…980b
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x3d1a7695…6409
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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 0xefb236ca8b…0ff49b
Audit this contract →
← previous block·next block →recent activity