← previous blocknext block →recent activity
Analyzing
Block #87,708,264
28 transactions · 21 stateful · 2026-07-14 13:24:24 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,708,264 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w010w112w214w117w218w324w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x06a0c880…707b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x86d1a3fb…ed61
0x34b655…2a6f
6 touches
3 conflicts
0x87bdb64a…593a
0x34b655…2a6f
6 touches
3 conflicts
0xa90aa7ad…403b
0x34b655…2a6f
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
6 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity