← previous blocknext block →recent activity
Analyzing
Block #87,621,406
19 transactions · 16 stateful · 2026-07-14 03:43:36 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,621,406 · 19 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
2w03w14w25w36w47w58w611w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xac61d3a4…7da8
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
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
8 touches
6 conflicts
0x68b75835…d6f3
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity