← previous blocknext block →recent activity
Analyzing
Block #87,621,709
14 transactions · 14 stateful · 2026-07-14 03:45:38 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,621,709 · 14 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
1w02w13w24w35w46w58w010w111w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac61d3a4…7da8
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x25329a48…4e00
0x34b655…2a6f
10 touches
10 conflicts
0x57179420…128a
0x34b655…2a6f
10 touches
10 conflicts
0x66ef954b…2d7a
0x34b655…2a6f
10 touches
10 conflicts
0x68b75835…d6f3
0x34b655…2a6f
10 touches
10 conflicts
0x79e62da8…efdc
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
15 conflicts on slot 0xac61d3a497…e97da8
Audit this contract →
← previous block·next block →recent activity