pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,351,514
← previous block
next block →
recent activity
Analyzing
Block #85,351,514
13 transactions · 12 stateful · 2026-07-03 15:03:43 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,351,514
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
0x957d4ba0
· blocks 1
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
0xed82b078
#9
modifyLiquidities
#10
setData
#11
execOrders
#12
0xc7e3ec2c
#3
0x957d4ba0
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a870d86…79ef
0x336ed4…c59c
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x2eb48eb7…9d68
0x8d1565…6723
4 touches
1 conflict
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0x8fa25c02…7f6d
0xa6afd3…d132
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:
0x336ed437…cfc59c
1 conflict on slot
0x4a870d863e…7379ef
Audit this contract →
← previous block
·
next block →
recent activity