pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,972,467
← previous block
next block →
recent activity
Analyzing
Block #72,972,467
13 transactions · 8 stateful · 2026-05-07 06:41:14 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,972,467
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute_route
#4
0x901cb3…56f0
#5
execute
#6
0x121eab2f
#7
0x69fc3482
#8
0x69fc3482
#9
updateDataFeedsValuesPartial
#10
0xeffdedb0
#11
setData
#12
execOrders
#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
0x1e5e118e…d011
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x06da6418…53ef
0x065c9d…c394
2 touches
0 conflicts
0x2d47e7a7…5bcc
0x065c9d…c394
2 touches
0 conflicts
0x596dc94b…e09e
0x065c9d…c394
2 touches
0 conflicts
0xc5c4c1d1…2145
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x1e5e118ea1…c7d011
Audit this contract →
← previous block
·
next block →
recent activity