pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,495,498
← previous block
next block →
recent activity
Analyzing
Block #98,495,498
35 transactions · 27 stateful · 2026-08-23 13:52:15 UTC
Parallelism
77
/100
Blocked
56
%
Avg conflicts / tx
1.06
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,495,498
· 35 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
batchCancelOrders
· blocks 1
#2
0x41a8f47c
· blocks 1
#3
0x41a8f47c
#4
execOrders
#5
0x8263f5d9
#6
execOrders
· blocks 4
#7
execOrder
· blocks 3
#9
0x59558d29
#11
0xe3a3c9cc
#12
0x0c7abd22
#13
0x0c7abd22
#14
0x0c7abd22
#15
0x5acec890
· blocks 3
#16
0x0c7abd22
#18
execOrder
#20
0x0c7abd22
· blocks 2
#21
updateDataFeedsValuesPartial
#27
0x0c7abd22
#28
setData
· blocks 1
#8
execOrder
· blocks 4
#10
0xb414539a
#17
0x5acec890
· blocks 3
#22
0x0c7abd22
· blocks 1
#23
0x3f5c179b
#29
setData
#30
execOrders
· blocks 4
#19
execOrder
· blocks 1
#24
0x0c7abd22
#26
execFwdPositionOpsV2
· blocks 1
#25
execFwdPositionOpsV2
· blocks 2
#31
execOrders
· blocks 3
#32
execOrders
· blocks 2
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
6
w0
7
w0
8
w1
10
w1
15
w0
17
w1
19
w2
20
w0
22
w1
23
w1
24
w2
25
w3
26
w2
30
w1
31
w4
32
w5
34
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x28fe17d2…4cc0
0x34b655…2a6f
6 touches
3 conflicts
0x080c3a8a…3088
0x34b655…2a6f
6 touches
3 conflicts
0xf8189834…f9db
0xd32edf…ff58
5 touches
3 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:
Perpl
10 conflicts on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity