pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,575,670
← previous block
next block →
recent activity
Analyzing
Block #84,575,670
14 transactions · 12 stateful · 2026-06-30 00:50:47 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,575,670
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xab083028
#4
updatePrices
#5
execOrders
· blocks 1
#6
execFwdPositionOps
#7
forward
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
0x6a43135f
· blocks 1
#11
setData
#12
0x6a43135f
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
10
w0
12
w1
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea2644f5…8c97
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x196004b8…e66e
0x065c9d…c394
2 touches
0 conflicts
0x247e4d3d…7313
0x065c9d…c394
2 touches
0 conflicts
0x32f9c1ec…9a63
0x065c9d…c394
2 touches
0 conflicts
0x4fe45763…b9d3
0x065c9d…c394
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
0xea2644f55c…128c97
Audit this contract →
← previous block
·
next block →
recent activity