← previous blocknext block →recent activity
Analyzing
Block #87,490,078
18 transactions · 17 stateful · 2026-07-13 13:04:29 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,490,078 · 18 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
3w04w15w06w27w39w010w111w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b33f5b9…4bab
0x34b655…2a6f
10 touches
10 conflicts
0x8c2d1205…a7b7
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x3cb4b659…f735
0x34b655…2a6f
6 touches
3 conflicts
0x3d4584df…ffed
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
10 conflicts on slot 0x5b33f5b941…b54bab
Audit this contract →
← previous block·next block →recent activity