pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,048,538
← previous block
next block →
recent activity
Analyzing
Block #87,048,538
10 transactions · 9 stateful · 2026-07-11 11:51:59 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
#87,048,538
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x1a945f9c
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
setData
#7
execFwdPositionOps
· blocks 1
#9
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59b0a8da…0928
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x002a0f9e…b33b
0xea1b8e…c5ec
2 touches
0 conflicts
0x1cbfa87c…f03a
0xea1b8e…c5ec
2 touches
0 conflicts
0x44fae103…87ad
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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
0x59b0a8da31…510928
Audit this contract →
← previous block
·
next block →
recent activity