← previous blocknext block →recent activity
Analyzing
Block #106,542,410
20 transactions · 18 stateful · 2026-09-20 19:06:57 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.45
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,542,410 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w19w110w211w312w413w514w615w716w817w919w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x527bf001…9976
0x34b655…2a6f
14 touches
21 conflicts
0x735a86cd…b64d
0x34b655…2a6f
14 touches
21 conflicts
0x4607e809…cc62
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xdbf974a4…b232
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x527bf00195…3a9976
Audit this contract →
← previous block·next block →recent activity