pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,563,462
← previous block
next block →
recent activity
Analyzing
Block #95,563,462
13 transactions · 11 stateful · 2026-08-13 06:47:32 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,563,462
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6bdec372
#2
execOrder
#3
execOrder
· blocks 2
#4
deposit
#6
updateDataFeedsValuesPartial
#8
forward
#9
0x26351b03
#10
transfer
#11
setData
#12
0x32366535
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xce54c462…7f74
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x19d0eecc…6863
0x34b655…2a6f
2 touches
0 conflicts
0x21885ba3…cb2f
0x34b655…2a6f
2 touches
0 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
2 touches
0 conflicts
0xa15e2d91…025a
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity