pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,333,012
← previous block
next block →
recent activity
Analyzing
Block #75,333,012
12 transactions · 9 stateful · 2026-05-18 05:12:57 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,333,012
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
transfer
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
addLiquidity
#6
exactInputSingle
#7
updatePriceFeedsIfNecessary
#8
closeTrade
#9
setData
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6195698…11a2
0x34b655…2a6f
4 touches
1 conflict
0x2f7781d6…e632
0x34b655…2a6f
3 touches
1 conflict
0x05e5ce66…b69e
0x2880ab…7b43
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0x676f9f01ee…dea8ac
Audit this contract →
← previous block
·
next block →
recent activity