pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,039,075
← previous block
next block →
recent activity
Analyzing
Block #73,039,075
17 transactions · 9 stateful · 2026-05-07 14:04:36 UTC
Parallelism
88
/100
Blocked
11
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,039,075
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
execPerpOps
#9
execPerpOps
#10
updateDataFeedsValuesPartial
#11
0x69fc9c6c
#12
0x85367786
· blocks 1
#14
0xeffdedb0
#15
setData
#16
execOrders
#13
0x85367786
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1755f056…5f8a
0x2c4667…b389
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x099c4e53…e9fe
0x2c4667…b389
2 touches
0 conflicts
0x4508dcd2…7c29
0x2c4667…b389
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
0x2c466769…99b389
1 conflict on slot
0x1755f05689…285f8a
Audit this contract →
← previous block
·
next block →
recent activity