pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,522,086
← previous block
next block →
recent activity
Analyzing
Block #95,522,086
10 transactions · 9 stateful · 2026-08-13 03:19:25 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,522,086
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#7
setData
#8
0x59558d29
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0xf62c017d…e543
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x3118505b…795e
0x34b655…2a6f
2 touches
0 conflicts
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
2 touches
0 conflicts
0x92a2c049…0ed8
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
0x0a57a2b8cd…773cdd
Audit this contract →
← previous block
·
next block →
recent activity