pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,707
← previous block
next block →
recent activity
Analyzing
Block #74,789,707
11 transactions · 8 stateful · 2026-05-15 16:43:46 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,707
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execPerpOps
#4
0x98717539
#5
transfer
#6
updateDataFeedsValuesPartial
#7
0x6a074dba
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x0f052239
#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
0x0631bceb…c321
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x50fe98a4…996f
0x065c9d…c394
2 touches
0 conflicts
0x74a63b2b…d9f3
0x065c9d…c394
2 touches
0 conflicts
0x976f577b…3916
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
0x0631bcebdb…88c321
Audit this contract →
← previous block
·
next block →
recent activity