pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,591,205
← previous block
next block →
recent activity
Analyzing
Block #80,591,205
14 transactions · 11 stateful · 2026-06-11 13:50:20 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,591,205
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
deposit
#2
0xab083028
#3
addLiquidity
#4
0x98717539
· blocks 1
#5
0x0c7abd22
#6
0x3f5c179b
#7
0x57368ddf
#8
0x3f5c179b
#10
execFwdPositionOps
#11
updateDataFeedsValuesPartial
#12
setData
#13
0x94e886…5a2a
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x51a80013…72b1
0x065c9d…c394
2 touches
0 conflicts
0xad7a04de…d9e4
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
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
0x90f07a4ff9…b3d932
Audit this contract →
← previous block
·
next block →
recent activity