pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,651,818
← previous block
next block →
recent activity
Analyzing
Block #80,651,818
11 transactions · 9 stateful · 2026-06-11 20:35:02 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,651,818
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
execOrders
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
0x57368ddf
#6
0x6a2b1c6e
#7
setData
#10
0xc7e3ec2c
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd6ccd20…c33e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7b3f8378…b37d
0x34b655…2a6f
4 touches
1 conflict
0x0ec53496…b8d2
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x22ac0643…fee7
0x34b655…2a6f
2 touches
0 conflicts
0x45460ec5…4bc9
0x34b655…2a6f
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
0xcd6ccd2062…74c33e
Audit this contract →
← previous block
·
next block →
recent activity