pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,296,753
← previous block
next block →
recent activity
Analyzing
Block #95,296,753
13 transactions · 11 stateful · 2026-08-12 08:21:40 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
#95,296,753
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
commitVerification
#2
0x6cfade05
#3
updatePrices
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
batchUpdate
#9
0x29eed2d3
#10
updateDataFeedsValuesPartial
#11
closeBetting
#12
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0x01b746a4…6c41
0x34b655…2a6f
2 touches
0 conflicts
0x06548ce0…bbd4
0x34b655…2a6f
2 touches
0 conflicts
0x0fc81850…e472
0x34b655…2a6f
2 touches
0 conflicts
0x1038d144…6054
0x34b655…2a6f
2 touches
0 conflicts
0x1526b11f…8b21
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity