pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,045,424
← previous block
next block →
recent activity
Analyzing
Block #71,045,424
11 transactions · 9 stateful · 2026-04-28 08:35:14 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
#71,045,424
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
execPerpOps
#4
0x98717539
#5
0x98717539
#6
0x0c7abd22
· blocks 1
#7
updateDataFeedsValuesPartial
#9
0x69f071ba
#10
setData
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9869660b…940d
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
2 touches
0 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
2 touches
0 conflicts
0x1c913164…5c2e
0x34b655…2a6f
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x313f2565…5b00
0x34b655…2a6f
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
0x9869660b95…df940d
Audit this contract →
← previous block
·
next block →
recent activity