← previous blocknext block →recent activity
Analyzing
Block #106,207,012
38 transactions · 31 stateful · 2026-09-19 14:58:55 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,207,012 · 38 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
1w02w13w07w110w011w216w319w122w225w326w427w428w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3faefef6…621c
0x34b655…2a6f
16 touches
28 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xb3610aa3…394f
0xd32edf…ff58
7 touches
6 conflicts
0x01cab646…0800
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 0x3faefef6cc…9b621c
Audit this contract →
← previous block·next block →recent activity