← previous blocknext block →recent activity
Analyzing
Block #87,489,777
22 transactions · 20 stateful · 2026-07-13 13:02:29 UTC
Parallelism
68/100
Blocked
30%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,489,777 · 22 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
3w06w011w112w213w314w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
6 touches
3 conflicts
0xf9d8ca45…db17
0x34b655…2a6f
6 touches
3 conflicts
0x9fe82ab3…218f
0x34b655…2a6f
4 touches
1 conflict
0xa24365bc…5064
0x34b655…2a6f
4 touches
1 conflict
0x2fe45c71…dc5a
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
3 conflicts on slot 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity