← previous blocknext block →recent activity
Analyzing
Block #87,621,779
26 transactions · 20 stateful · 2026-07-14 03:46:06 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,779 · 26 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
1w05w012w013w114w115w216w317w118w422w023w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x640530ff…86bc
0x34b655…2a6f
8 touches
6 conflicts
0xf2f40f08…5cdb
0x34b655…2a6f
6 touches
3 conflicts
0x1d15e8b9…e219
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x3f4d9d89…7299
0x34b655…2a6f
4 touches
1 conflict
0x55679433…d91f
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity