← previous blocknext block →recent activity
Analyzing
Block #106,772,034
21 transactions · 21 stateful · 2026-09-21 14:23:35 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,772,034 · 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
1w02w03w14w25w38w39w412w413w114w515w216w517w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x34c48330…703f
0x34b655…2a6f
8 touches
6 conflicts
0xa486eb22…db27
0x34b655…2a6f
8 touches
6 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
8 touches
6 conflicts
0xaa9bb801…1a57
0x34b655…2a6f
6 touches
3 conflicts
0xb480d016…0fce
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity