pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,629,017
← previous block
next block →
recent activity
Analyzing
Block #97,629,017
11 transactions · 10 stateful · 2026-08-20 12:47:14 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,629,017
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
· blocks 1
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
0x59558d29
#10
execOrders
#3
0x6ad2e98b
· blocks 1
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- 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…003d
0x851145…3f07
4 touches
1 conflict
0x31762a87…3704
0x851145…3f07
4 touches
1 conflict
0x90b1f042…5833
0x851145…3f07
4 touches
1 conflict
0xa75c1cae…5eed
0x851145…3f07
3 touches
1 conflict
0x2f74f175…9284
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9285
0x2b46c0…1669
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity