pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,624,510
← previous block
next block →
recent activity
Analyzing
Block #96,624,510
13 transactions · 11 stateful · 2026-08-16 23:46:08 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
#96,624,510
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrder
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
execOrders
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
0xed82b078
#12
setData
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x13a157e0…215b
0x34b655…2a6f
2 touches
0 conflicts
0x4b54bf38…d5b6
0x34b655…2a6f
2 touches
0 conflicts
0x508c93c4…79f4
0x34b655…2a6f
2 touches
0 conflicts
0x56153262…21ce
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
0xb3fb9fb561…7664db
Audit this contract →
← previous block
·
next block →
recent activity