pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,171,064
← previous block
next block →
recent activity
Analyzing
Block #99,171,064
13 transactions · 11 stateful · 2026-08-25 23:13:59 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,171,064
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
updatePrices
#3
0xab083028
#4
0x5acec890
· blocks 1
#5
execOrders
#6
batchUpdate
#8
execFwdPositionOpsV2
#9
0x6a8e222f
#10
setData
#11
setData
#12
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00e5ba9d…5f4e
0x34b655…2a6f
2 touches
0 conflicts
0x059e0ac0…0267
0x34b655…2a6f
2 touches
0 conflicts
0x1634c5ef…777a
0x34b655…2a6f
2 touches
0 conflicts
0x1f396cee…862f
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
0xf4b2a42760…660234
Audit this contract →
← previous block
·
next block →
recent activity