pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,691,719
← previous block
next block →
recent activity
Analyzing
Block #86,691,719
10 transactions · 9 stateful · 2026-07-09 20:07:30 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,691,719
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
0x6a4ffffa
#8
startRound
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6633
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6632
0x34b655…2a6f
4 touches
1 conflict
0xdf8b6ee1…84d2
0x34b655…2a6f
4 touches
1 conflict
0x9c979474…fed6
0x34b655…2a6f
3 touches
1 conflict
0xef75b5d0…07b7
0x40c49f…2af0
2 touches
0 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
1 conflict on slot
0x921a58d196…62db22
Audit this contract →
← previous block
·
next block →
recent activity