pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,490,843
← previous block
next block →
recent activity
Analyzing
Block #98,490,843
38 transactions · 28 stateful · 2026-08-23 13:28:50 UTC
Parallelism
87
/100
Blocked
50
%
Avg conflicts / tx
0.68
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,490,843
· 38 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x6a8af60a
#2
0xd524a9da
#3
0x41a8f47c
#4
execOrders
· blocks 2
#6
0xab083028
· blocks 3
#7
0x8263f5d9
#8
execOrders
· blocks 3
#11
0x0c7abd22
· blocks 1
#12
execOrder
· blocks 2
#13
0x59558d29
#14
execPerpOps
#15
execPerpOps
#16
execPerpOps
#17
execPerpOps
#18
approve
#19
0x0c7abd22
#20
0x0c7abd22
#21
0x0c7abd22
#24
execOrder
#27
0x3f5c179b
#29
0x0c7abd22
#34
setData
#35
execOrders
#5
execOrders
· blocks 3
#9
execOrders
· blocks 1
#22
0x5acec890
· blocks 2
#26
execFwdPositionOpsV2
· blocks 1
#28
0x0c7abd22
· blocks 2
#10
execOrders
#23
0x5acec890
· blocks 2
#30
execFwdPositionOpsV2
· blocks 1
#32
0xed82b078
· blocks 1
#25
0x928e4afa
· blocks 1
#31
execFwdPositionOpsV2
#33
0xed82b078
#36
execOrders
· blocks 1
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
8
w0
9
w1
10
w2
11
w0
12
w0
22
w1
23
w2
25
w3
26
w1
28
w1
30
w2
31
w3
32
w2
33
w3
36
w3
37
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x316191c8…66c8
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x0747620e…9782
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: Market-MON/USDC
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity