← previous blocknext block →recent activity
Analyzing
Block #87,700,255
50 transactions · 39 stateful · 2026-07-14 12:30:37 UTC
Parallelism
78/100
Blocked
62%
Avg conflicts / tx
1.32
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,700,255 · 50 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w010w112w214w315w419w125w136w237w239w241w542w343w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0x166f610d…690f
0x34b655…2a6f
8 touches
6 conflicts
0x40ee7a94…d6a8
0x34b655…2a6f
8 touches
6 conflicts
0x442e26a3…e968
0x34b655…2a6f
8 touches
6 conflicts
0x4b90e63c…c17d
0x34b655…2a6f
8 touches
6 conflicts
0x542ff3d0…3fa7
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity