pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,745,606
← previous block
next block →
recent activity
Analyzing
Block #85,745,606
10 transactions · 6 stateful · 2026-07-05 10:49:07 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,745,606
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#6
setData
#7
0x97b39e…1ef2
#8
0xeb1941…c044
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x444668fd…8dc9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x10f4fcbf…fe5d
0x34b655…2a6f
2 touches
0 conflicts
0x15c8c3bc…7175
0x34b655…2a6f
2 touches
0 conflicts
0x2b8ae238…b119
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
0x444668fd4f…478dc9
Audit this contract →
← previous block
·
next block →
recent activity