← previous blocknext block →recent activity
Analyzing
Block #87,616,110
24 transactions · 19 stateful · 2026-07-14 03:08:13 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,110 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w611w012w113w214w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xa0af25f7…9129
0x34b655…2a6f
10 touches
10 conflicts
0xa0c6e179…a103
0x34b655…2a6f
10 touches
10 conflicts
0x2a513dfb…2bb8
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x1175233a…64e7
0x34b655…2a6f
10 touches
10 conflicts
0xd379a368…fea4
0x34b655…2a6f
10 touches
10 conflicts
0x25329a48…4e00
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity