pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,045,663
← previous block
next block →
recent activity
Analyzing
Block #71,045,663
15 transactions · 14 stateful · 2026-04-28 08:36:50 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,045,663
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
exactOutputSingle
#4
updatePrices
#5
execPerpOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
exactInputSingle
#9
0x69f07219
#10
setData
#11
execOrders
#12
updatePrices
· blocks 1
#13
updatePrices
#6
execPerpOps
#14
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
12
w0
14
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x60fad943…47d2
0x065c9d…c394
2 touches
0 conflicts
0x65076518…320d
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:
Perpl
1 conflict on slot
0xea02471df2…601539
Audit this contract →
← previous block
·
next block →
recent activity