pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,915,742
← previous block
next block →
recent activity
Analyzing
Block #95,915,742
24 transactions · 13 stateful · 2026-08-14 12:20:44 UTC
Parallelism
92
/100
Blocked
23
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,915,742
· 24 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4fa451…4a37
#2
0xa9b28aa6
#3
0x693c2be6
#4
0x00771418
#5
0xf8b1083e
#6
0x05ee6a22
#7
0x05ee6a22
#8
0xab083028
· blocks 1
#9
0x50a0b275
#10
0xb414539a
#11
execPerpOps
#12
execPerpOps
#13
0x0c7abd22
· blocks 1
#14
execOrders
#15
updateDataFeedsValuesPartial
#16
updateDataFeedsValuesPartial
#17
execFwdPositionOpsV2
· blocks 1
#18
execFwdPositionOpsV2
· blocks 1
#19
0x62be7533
#23
setData
#20
execFwdPositionOpsV2
#21
0x0c7abd22
#22
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
13
w0
17
w0
18
w0
20
w1
21
w1
22
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xe0b49f38…d4de
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0002
0x04ddf6…7f33
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity