pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,865,076
← previous block
next block →
recent activity
Analyzing
Block #75,865,076
11 transactions · 9 stateful · 2026-05-20 16:31:39 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,865,076
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
forward
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#8
setData
#9
execOrders
· blocks 1
#2
execPerpOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x4d7d1066…4e72
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
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
0x451e482b59…427e7d
Audit this contract →
← previous block
·
next block →
recent activity