pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,037,455
← previous block
next block →
recent activity
Analyzing
Block #96,037,455
11 transactions · 11 stateful · 2026-08-14 22:33:10 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,037,455
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
execOrders
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#8
execFwdPositionOpsV2
#9
transfer
#10
setData
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x750fb05c…0e99
0x34b655…2a6f
4 touches
1 conflict
0x704db644…309a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x454cdf57…aebc
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x8ea794f6…38d1
0x34b655…2a6f
2 touches
0 conflicts
0x91ee3bb1…a20d
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
0x750fb05c31…040e99
Audit this contract →
← previous block
·
next block →
recent activity