← previous blocknext block →recent activity
Analyzing
Block #87,520,331
23 transactions · 21 stateful · 2026-07-13 16:27:10 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,520,331 · 23 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
2w03w14w25w36w48w09w011w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
10 touches
10 conflicts
0x18904470…0ef9
0x34b655…2a6f
8 touches
6 conflicts
0x10fec71b…e12f
0x34b655…2a6f
6 touches
3 conflicts
0x169d3880…b580
0x34b655…2a6f
6 touches
3 conflicts
0x39c4bc47…ce30
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0xca18c58e…cede
0x34b655…2a6f
6 touches
3 conflicts
0xd2453506…54e4
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 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity