← previous blocknext block →recent activity
Analyzing
Block #87,725,013
20 transactions · 17 stateful · 2026-07-14 15:16:36 UTC
Parallelism
60/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,725,013 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
10 touches
10 conflicts
0x2f35c56f…046b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x59a462ca…c93f
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1659
0x34b655…2a6f
6 touches
3 conflicts
0xcc6e2e88…6569
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 0xc9dce17a10…8ca1a1
Audit this contract →
← previous block·next block →recent activity