← previous blocknext block →recent activity
Analyzing
Block #106,189,159
21 transactions · 21 stateful · 2026-09-19 13:29:01 UTC
Parallelism
76/100
Blocked
62%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,189,159 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w18w211w113w214w315w316w419w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fcbf9b2…a36e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0626b6f1…c870
0xd32edf…ff58
7 touches
6 conflicts
0xbf5419db…6b18
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x3f152ba8…cea6
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 0x8fcbf9b2e6…d7a36e
Audit this contract →
← previous block·next block →recent activity