pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,455,727
← previous block
next block →
recent activity
Analyzing
Block #99,455,727
36 transactions · 25 stateful · 2026-08-26 23:06:48 UTC
Parallelism
75
/100
Blocked
52
%
Avg conflicts / tx
0.58
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,455,727
· 36 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x4f819052
· blocks 1
#2
0xd524a9da
#3
executePacked
#5
0x41a8f47c
#6
0x50a0b275
#7
0x6a8f7200
#9
0xab083028
#10
0x32d01e04
#11
execOrders
· blocks 1
#13
0x5acec890
· blocks 3
#15
0x5acec890
#17
execOrders
#18
0x59558d29
#19
execPerpOps
#20
execPerpOps
#21
0xe3a3c9cc
#22
execOrders
#23
execOrders
#24
execFwdPositionOpsV2
#26
0x62be7533
#28
0x3f5c179b
#32
setData
#4
0xab083028
· blocks 3
#12
execOrders
· blocks 1
#27
execFwdPositionOpsV2
#8
0x6ad2e98b
#14
0x5acec890
· blocks 2
#29
0x0c7abd22
· blocks 1
#16
0x928e4afa
· blocks 2
#30
0xed82b078
#25
execFwdPositionOpsV2
· blocks 3
#31
execFwdPositionOpsV2
· blocks 1
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
8
w2
11
w0
12
w1
13
w0
14
w2
16
w3
25
w4
27
w1
29
w2
30
w3
31
w5
33
w6
34
w7
35
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x498ed94c…967d
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity