pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,502,647
← previous block
next block →
recent activity
Analyzing
Block #73,502,647
14 transactions · 6 stateful · 2026-05-09 17:29:03 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,502,647
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
execute_route
#3
0xe7be4706
#4
0xe7be4706
#5
0xe7be4706
· blocks 1
#6
0xe7be4706
#7
0xe7be4706
#9
updateDataFeedsValuesPartial
#10
0x62be7533
#11
0xe9316489
#12
setData
#13
0x39435dac
#8
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0xd56db188…ecd0
0x000000…012a
2 touches
0 conflicts
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
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:
Wrapped MON (WMON)
1 conflict on slot
0x0d0b2509ae…4b074d
Audit this contract →
← previous block
·
next block →
recent activity