pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,911,718
← previous block
next block →
recent activity
Analyzing
Block #85,911,718
13 transactions · 10 stateful · 2026-07-06 05:15:25 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,911,718
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrder
#3
0x62be7533
· blocks 1
#4
0x3f5c179b
#5
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x7fa35b…b7b2
#11
0xd6561e…a3d3
#12
execOrders
#6
settle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x48c3bb…b17b
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xdd43be87…f667
0xe1c8b7…3022
3 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
Wrapped MON (WMON)
1 conflict on slot
0xc6101b5dc8…d04361
Audit this contract →
← previous block
·
next block →
recent activity