pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,684,654
← previous block
next block →
recent activity
Analyzing
Block #96,684,654
10 transactions · 9 stateful · 2026-08-17 04:48:37 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,684,654
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
execOrder
#4
execOrders
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x61d59c2d
#2
0x8263f5d9
#6
execFwdPositionOpsV2
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x3f2796bf…f0fa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity