pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,731,114
← previous block
next block →
recent activity
Analyzing
Block #97,731,114
20 transactions · 18 stateful · 2026-08-20 21:30:43 UTC
Parallelism
85
/100
Blocked
28
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,731,114
· 20 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x7b84f330
· blocks 1
#4
updatePrices
#5
execOrders
#6
0xab083028
#7
execOrders
#8
transfer
#9
0x5acec890
#10
updateDataFeedsValuesPartial
#11
execFwdPositionOpsV2
#13
execFwdPositionOpsV2
· blocks 1
#14
setData
#15
0x59558d29
#17
execOrders
#2
0x0c7abd22
· blocks 1
#16
execOrders
· blocks 1
#19
0x7b84f330
#12
0xed82b078
#18
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
12
w2
13
w0
16
w1
18
w2
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0adfec5f…8741
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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
3 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity