pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,344,509
← previous block
next block →
recent activity
Analyzing
Block #85,344,509
11 transactions · 9 stateful · 2026-07-03 14:17:02 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
#85,344,509
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5b949537
#5
execFwdPositionOps
· blocks 1
#6
0xee83e0a5
#7
execFwdPositionOps
#8
0x6a47c4d6
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xa0bf4c78…28e7
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0174cd11…8caf
0x103222…7496
2 touches
0 conflicts
0xbb6b5cc3…4c49
0x103222…7496
2 touches
0 conflicts
0x0b1116a0…ca0a
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
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
0xda2ee2e777…e7968a
Audit this contract →
← previous block
·
next block →
recent activity