← previous blocknext block →recent activity
Analyzing
Block #106,408,207
33 transactions · 29 stateful · 2026-09-20 07:51:28 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,408,207 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w110w215w318w319w424w226w427w528w629w732w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fc2bb7…c2c2
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
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
28 conflicts on slot 0x05fc2bb7ca…43c2c2
Audit this contract →
← previous block·next block →recent activity