pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,733,965
← previous block
next block →
recent activity
Analyzing
Block #97,733,965
11 transactions · 11 stateful · 2026-08-20 21:45:03 UTC
Parallelism
82
/100
Blocked
36
%
Avg conflicts / tx
0.36
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,733,965
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x6ad2e98b
#3
execOrder
· blocks 2
#4
batchUpdate
· blocks 1
#7
setData
#8
0x61d59c2d
#5
execFwdPositionOpsV2
#6
0xed82b078
#9
execOrders
#10
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w0
5
w1
6
w1
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9f92647…5b01
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x72ec2001…6792
0x40c49f…2af0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0x1ab4c88c…49f3
0x34b655…2a6f
2 touches
0 conflicts
0x403a76dd…6473
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
0xe9f926479e…105b01
Audit this contract →
← previous block
·
next block →
recent activity