pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,797,640
← previous block
next block →
recent activity
Analyzing
Block #85,797,640
11 transactions · 9 stateful · 2026-07-05 16:35:34 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,797,640
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6ad2e98b
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
0x041f34…2b9d
#7
0xed82b078
#8
setData
#9
0xa66045…414d
#10
0x39435dac
#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
0xbc7d22db…cb31
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
0x0ede4d0d…bfe7
0x065c9d…c394
2 touches
0 conflicts
0x15356c84…0e36
0x065c9d…c394
2 touches
0 conflicts
0x2acfa091…d7e4
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
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
0xbc7d22db45…1ccb31
Audit this contract →
← previous block
·
next block →
recent activity