pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,309,371
← previous block
next block →
recent activity
Analyzing
Block #99,309,371
40 transactions · 28 stateful · 2026-08-26 10:49:53 UTC
Parallelism
92
/100
Blocked
46
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,309,371
· 40 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x7d619a…b626
#2
0x4f819052
· blocks 3
#3
0xbe5a93b8
#4
0x6a8ec549
#5
0x6a8ec549
#6
0x6a8ec549
#7
main_all
#8
updatePrices
· blocks 2
#10
updatePrices
#12
updatePrices
#13
0xefdb8189
#14
0xab083028
· blocks 2
#17
0x8263f5d9
#18
execOrders
· blocks 1
#21
0x5acec890
· blocks 1
#22
execOrder
· blocks 1
#24
execPerpOps
· blocks 1
#26
execFwdPositionOpsV2
#27
execFwdPositionOpsV2
#29
0x3f5c179b
· blocks 1
#30
redeemDelegations
#31
predictAndBet
#33
0xed82b078
#35
execFwdPositionOpsV2
#36
setData
#37
execOrders
#9
updatePrices
· blocks 1
#15
0xab083028
· blocks 1
#19
execOrders
#20
0x0c7abd22
· blocks 1
#23
execOrder
#25
execPerpOps
#28
updatePosition
#32
batchUpdate
#38
execOrders
· blocks 1
#11
updatePrices
#16
0x32d01e04
#34
0xed82b078
#39
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w0
9
w1
11
w2
14
w0
15
w1
16
w2
18
w0
19
w1
20
w1
21
w0
22
w0
23
w1
24
w0
25
w1
28
w1
29
w0
32
w1
34
w2
38
w1
39
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6d5647f9…9450
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
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:
0xf5b5f7f8…a36d70
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity