pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,492,452
← previous block
next block →
recent activity
Analyzing
Block #84,492,452
14 transactions · 11 stateful · 2026-06-29 15:35:19 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,492,452
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
updatePrices
#6
0x6a42912f
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
execOrders
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfee13cc…8246
0xa70f46…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x452e7d5d…8e22
0x34b655…2a6f
2 touches
0 conflicts
0x5fe13be2…f3cf
0x34b655…2a6f
2 touches
0 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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:
0xa70f4653…c87777
1 conflict on slot
0xcfee13ccf0…b98246
Audit this contract →
← previous block
·
next block →
recent activity