pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,307,376
← previous block
next block →
recent activity
Analyzing
Block #99,307,376
27 transactions · 21 stateful · 2026-08-26 10:39:51 UTC
Parallelism
81
/100
Blocked
24
%
Avg conflicts / tx
0.3
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,307,376
· 27 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xf78cb219
· blocks 3
#2
0x0b89a1…03dc
#3
execute
#5
main_all
#6
updatePrices
#7
0x6ad2e98b
#10
execOrders
#11
0x5acec890
#12
execOrders
#13
execPerpOps
#14
0x6cfade05
#15
execPerpOps
#16
execPerpOps
#17
updateDataFeedsValuesPartial
#18
redeemDelegations
#19
0x62be7533
#20
execFwdPositionOpsV2
#21
execFwdPositionOpsV2
#23
forward
#25
0x6a8ec2ee
#26
setData
#4
0xaf5e395a
· blocks 2
#8
0xab083028
· blocks 2
#9
0xab083028
· blocks 1
#24
batchUpdate
#22
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
8
w2
9
w3
22
w4
24
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xf46c4ea7…d9dd
0x065c9d…c394
5 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf6966c4f…b3f3
0x40c49f…2af0
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
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity