pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,477,333
← previous block
next block →
recent activity
Analyzing
Block #73,477,333
11 transactions · 8 stateful · 2026-05-09 14:40:29 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,477,333
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x16040cc9
· blocks 2
#4
updateDataFeedsValuesPartial
#5
execPerpOps
#6
execPerpOps
#7
setData
#8
verifyOracleProofV2
#9
0x69ff47d5
#10
0xd2ef84…f824
#2
0x16040cc9
· blocks 1
#3
0x16040cc9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x714a26…182d
6 touches
3 conflicts
0x4c770fe0…b972
0x3bd359…433a
6 touches
3 conflicts
0x392a02b5…0019
0x81a224…7777
6 touches
3 conflicts
0x00000000…0000
0x714a26…182d
6 touches
3 conflicts
0x00000000…0001
0x714a26…182d
6 touches
3 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…641c
0x34b655…2a6f
2 touches
0 conflicts
0xd5076d79…8bd3
0x58e158…3d57
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:
0x714a2694…f2182d
3 conflicts on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity