pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,864,606
← previous block
next block →
recent activity
Analyzing
Block #95,864,606
12 transactions · 10 stateful · 2026-08-14 08:03:15 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,864,606
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrder
#3
execOrder
· blocks 2
#5
updatePrices
· blocks 1
#7
updateDataFeedsValuesPartial
#8
exactInputSingle
#9
batchUpdate
#11
setData
#4
execOrder
#6
updatePrices
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b6a024…9739
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x1fa581e1…53d8
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x8b98eea2…60b0
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
0x24b6a024cf…889739
Audit this contract →
← previous block
·
next block →
recent activity