← previous blocknext block →recent activity
Analyzing
Block #87,306,035
21 transactions · 19 stateful · 2026-07-12 16:33:44 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,306,035 · 21 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
2w03w14w05w26w37w48w59w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x351fa26b…2018
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0xb8e24fcc…4687
0x34b655…2a6f
8 touches
6 conflicts
0xb91a6f59…722c
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
6 conflicts on slot 0x351fa26be6…a82018
Audit this contract →
← previous block·next block →recent activity