← previous blocknext block →recent activity
Analyzing
Block #87,715,163
31 transactions · 27 stateful · 2026-07-14 14:10:36 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,715,163 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w27w08w19w010w111w012w113w214w315w416w517w618w719w824w926w228w130w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aa5ecc1…1b3d
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc6c81e93…9b2f
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xdb529f62…663c
0x34b655…2a6f
8 touches
6 conflicts
0xfebaf6fc…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
21 conflicts on slot 0x1aa5ecc1d1…d51b3d
Audit this contract →
← previous block·next block →recent activity