pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,652,952
← previous block
next block →
recent activity
Analyzing
Block #80,652,952
14 transactions · 8 stateful · 2026-06-11 20:42:34 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,652,952
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0xe2dc7dc3
#10
0x98717539
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#2
updatePrices
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
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x207e7985…b608
0x1efe02…37d6
2 touches
0 conflicts
0x2a2bacfe…6a55
0x1efe02…37d6
2 touches
0 conflicts
0x357ef718…5a36
0x1efe02…37d6
2 touches
0 conflicts
0x5922d542…53e2
0x1efe02…37d6
2 touches
0 conflicts
0x5f53a383…ac9b
0x1efe02…37d6
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:
0x6fae9933…7ba56d
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity