← previous blocknext block →recent activity
Analyzing
Block #87,750,925
16 transactions · 15 stateful · 2026-07-14 18:09:58 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,750,925 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w39w410w411w512w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d3df40a…28cb
0x34b655…2a6f
12 touches
15 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x806bf739…e950
0x34b655…2a6f
6 touches
3 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
6 touches
3 conflicts
0x4ce41dcc…e297
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
15 conflicts on slot 0x3d3df40a23…8a28cb
Audit this contract →
← previous block·next block →recent activity