pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,969,008
← previous block
next block →
recent activity
Analyzing
Block #86,969,008
11 transactions · 9 stateful · 2026-07-11 03:00:35 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,969,008
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0x0f6795d9
#7
setData
#8
0x57368ddf
#10
0x6a51b24b
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa412324b…90ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa412324b…90aa
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0xe2ce91e2…b99e
0x34b655…2a6f
4 touches
1 conflict
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0x4dc57c26…85d1
0x34b655…2a6f
3 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
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
0xa412324b83…4590ab
Audit this contract →
← previous block
·
next block →
recent activity