pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,906,061
← previous block
next block →
recent activity
Analyzing
Block #85,906,061
12 transactions · 9 stateful · 2026-07-06 04:37:45 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,906,061
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
updatePrices
#3
execOrder
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
execFwdPositionOps
#9
0xed82b078
#10
setData
#4
execOrder
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x2d8487d0…24c6
0x34b655…2a6f
3 touches
1 conflict
0x03da8cec…05df
0x34b655…2a6f
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x7aad02c6…b979
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
0x1aaf499609…4665ec
Audit this contract →
← previous block
·
next block →
recent activity