← previous blocknext block →recent activity
Analyzing
Block #106,772,425
21 transactions · 19 stateful · 2026-09-21 14:25:33 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,772,425 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w18w19w210w313w314w116w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0e59c55…2dca
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x1f4c5f88…54af
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2d764ee6…54ac
0x34b655…2a6f
6 touches
3 conflicts
0x18a1397a…c0aa
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd0e59c55f8…a92dca
Audit this contract →
← previous block·next block →recent activity