pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,262,089
← previous block
next block →
recent activity
Analyzing
Block #96,262,089
9 transactions · 8 stateful · 2026-08-15 17:23:01 UTC
Parallelism
78
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,262,089
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 2
#5
execFwdPositionOpsV2
#6
setData
#2
execOrders
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x9cc7f46d…3267
0x34b655…2a6f
4 touches
1 conflict
0x8824d58e…fc00
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
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
0x83f3d32000…25fb59
Audit this contract →
← previous block
·
next block →
recent activity