pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,635,196
← previous block
next block →
recent activity
Analyzing
Block #81,635,196
10 transactions · 9 stateful · 2026-06-16 09:46:52 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,635,196
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xea5760…f9eb
#2
0xab083028
#3
updatePrices
#4
execOrders
#5
updateDataFeedsValuesPartial
#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
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x897df0ee…b0c5
0x40c49f…2af0
2 touches
0 conflicts
0x92bb2968…6e62
0x40c49f…2af0
2 touches
0 conflicts
0x9b03a6d5…d8ed
0x40c49f…2af0
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
0x6637e421bf…b0af93
Audit this contract →
← previous block
·
next block →
recent activity