pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,036,688
← previous block
next block →
recent activity
Analyzing
Block #73,036,688
15 transactions · 12 stateful · 2026-05-07 13:48:42 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,036,688
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fc98b2
· blocks 2
#3
execute
#4
exactOutputSingle
#5
execute
#6
0xe7be4706
#7
updateDataFeedsValuesPartial
#8
0x366fe5db
#9
forward
#10
forward
#11
modifyLiquidities
#12
0xeffdedb0
#13
setData
#2
0x69fc98b2
· blocks 1
#14
0x69fc98b2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
14
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a996
0x188d58…ea8e
2 touches
0 conflicts
0xb1acfe51…c6b1
0x3bd359…433a
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:
0x681e908b…e1ae09
3 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity