pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,707,624
← previous block
next block →
recent activity
Analyzing
Block #96,707,624
10 transactions · 8 stateful · 2026-08-17 06:44:09 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,707,624
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#8
transfer
#9
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04f6d949…d859
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x0939bc15…c5e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a6829a0…3569
0x34b655…2a6f
2 touches
0 conflicts
0x0aa42ae9…ed69
0x34b655…2a6f
2 touches
0 conflicts
0x13a3bd59…8bab
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
0x04f6d949c9…eed859
Audit this contract →
← previous block
·
next block →
recent activity