pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,968,503
← previous block
next block →
recent activity
Analyzing
Block #86,968,503
12 transactions · 12 stateful · 2026-07-11 02:57:13 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,968,503
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
cancel
#7
execFwdPositionOps
#9
0x0cf032c6
#10
setData
#11
execOrders
#2
0x0c7abd22
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x008accc4…1da8
0x34b655…2a6f
4 touches
1 conflict
0x2c5edd82…074a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa2f6dacc…12fc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x89743ce4…cea2
0xd32edf…ff58
3 touches
1 conflict
0x4faed5b4…61de
0x065c9d…c394
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
0x008accc476…b51da7
Audit this contract →
← previous block
·
next block →
recent activity