← previous blocknext block →recent activity
Analyzing
Block #87,621,385
22 transactions · 21 stateful · 2026-07-14 03:43:28 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,621,385 · 22 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
1w05w06w17w28w311w412w513w114w615w719w220w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9fe0433…7f01
0x34b655…2a6f
10 touches
10 conflicts
0x18e900fa…07f4
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x25329a48…4e00
0x34b655…2a6f
8 touches
6 conflicts
0x5e03a380…a551
0x34b655…2a6f
8 touches
6 conflicts
0x68b75835…d6f3
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
8 touches
6 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 0xc9fe0433ca…417f01
Audit this contract →
← previous block·next block →recent activity