pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,326,841
← previous block
next block →
recent activity
Analyzing
Block #80,326,841
13 transactions · 11 stateful · 2026-06-10 08:27:49 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,326,841
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x6a29207d
#4
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
updatePriceFeedsIfNecessary
#9
executeBatch
#10
setData
#11
execOrders
#12
0xc7e3ec2c
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69e
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccb
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: Settlement / Helper
1 conflict on slot
0xc38151f296…e92bcb
Audit this contract →
← previous block
·
next block →
recent activity