pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,461,749
← previous block
next block →
recent activity
Analyzing
Block #84,461,749
12 transactions · 11 stateful · 2026-06-29 12:10:27 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,461,749
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
main_all
#2
0x6ad2e98b
#3
execOrders
· blocks 2
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0xed82b078
#9
0x6a42612b
· blocks 1
#11
setData
#4
execOrders
#6
execFwdPositionOps
#10
0x6a42612b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa8279ae9…f9f9
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x93d680fb…ac21
0x34b655…2a6f
4 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0xe60cff44…1b50
0x57ea24…2cec
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity