pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,841,832
← previous block
next block →
recent activity
Analyzing
Block #97,841,832
16 transactions · 16 stateful · 2026-08-21 06:49:42 UTC
Parallelism
88
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,841,832
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x6ad2e98b
#4
execOrders
#5
0xb2d4797b
#6
0x928e4afa
· blocks 1
#7
redeemDelegations
#9
buy
#10
0x57368ddf
#11
forward
#12
forward
#13
setData
#14
0x59558d29
#15
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfcbbba99…6047
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x260cc5c4…bef0
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186a
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186d
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:
Perpl
1 conflict on slot
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity