← previous blocknext block →recent activity
Analyzing
Block #87,497,519
31 transactions · 28 stateful · 2026-07-13 13:54:17 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,497,519 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w08w111w214w115w216w317w420w521w623w424w126w527w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x518f2037…e422
0xa6afd3…d132
8 touches
6 conflicts
0x66f473d3…2d03
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x5b9e45d3…6b77
0x34b655…2a6f
6 touches
3 conflicts
0x6de059e6…1d12
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity