← previous blocknext block →recent activity
Analyzing
Block #87,421,139
50 transactions · 39 stateful · 2026-07-13 05:23:34 UTC
Parallelism
88/100
Blocked
62%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,421,139 · 50 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
1w03w15w06w210w211w012w113w214w315w016w117w218w320w021w123w234w435w136w346w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x9f897589…6981
0xd32edf…ff58
7 touches
6 conflicts
0x213ee207…a151
0x2b46c0…1669
6 touches
3 conflicts
0x7b6b88fb…1109
0x2b46c0…1669
6 touches
3 conflicts
0xb55a7cbc…68f5
0x2b46c0…1669
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity