pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,481,749
← previous block
next block →
recent activity
Analyzing
Block #80,481,749
10 transactions · 8 stateful · 2026-06-11 01:39:57 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,481,749
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
0x1a945f9c
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
setData
#7
execOrders
· blocks 1
#9
0xc7e3ec2c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x18b11fba…c92a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x86dba61b…01be
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0x92422ced…8761
0x754704…b603
2 touches
0 conflicts
0xf653ebdf…16c7
0x754704…b603
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity