pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,041,496
← previous block
next block →
recent activity
Analyzing
Block #73,041,496
10 transactions · 8 stateful · 2026-05-07 14:20:40 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,496
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
updatePrices
#2
0x1a945f9c
#3
updateIndexData
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#7
0xeffdedb0
#8
setData
#9
execOrders
#6
compound
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x208e6baf…e5fa
0x1efe02…37d6
2 touches
0 conflicts
0x5c04a735…023f
0x1efe02…37d6
2 touches
0 conflicts
0xb8a0b1ac…1f03
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x8415a8e2…a326
0xaa3145…feec
2 touches
0 conflicts
0x00000000…0002
0xd574ca…7ab1
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:
Monad: Staking
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity