pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,479,998
← previous block
next block →
recent activity
Analyzing
Block #81,479,998
8 transactions · 5 stateful · 2026-06-15 16:33:13 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,479,998
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
setData
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
updatePriceFeedsIfNecessary
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb0fe1e4…7dab
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x008d1373…3c83
0x34b655…2a6f
2 touches
0 conflicts
0x132c6c23…8382
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x30a02fb0…7c3d
0x34b655…2a6f
2 touches
0 conflicts
0x421da1f7…aabe
0x34b655…2a6f
2 touches
0 conflicts
0x614471d1…0558
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:
Perpl
1 conflict on slot
0xeb0fe1e443…a47dab
Audit this contract →
← previous block
·
next block →
recent activity