pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,418,291
← previous block
next block →
recent activity
Analyzing
Block #73,418,291
10 transactions · 8 stateful · 2026-05-09 08:07:45 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,418,291
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
0x54cb092e
#9
setData
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea5bc388…0a70
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x84956c3a…6ced
0x065c9d…c394
2 touches
0 conflicts
0x9b42b9c9…fca8
0x065c9d…c394
2 touches
0 conflicts
0xb02e5f81…3197
0x065c9d…c394
2 touches
0 conflicts
0xca656d84…60ac
0x065c9d…c394
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0xea5bc3885b…410a70
Audit this contract →
← previous block
·
next block →
recent activity