pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,929,170
← previous block
next block →
recent activity
Analyzing
Block #98,929,170
38 transactions · 30 stateful · 2026-08-25 02:50:16 UTC
Parallelism
84
/100
Blocked
53
%
Avg conflicts / tx
0.55
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,929,170
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x41a8f47c
#2
0x41a8f47c
#3
0x5acec890
· blocks 3
#4
updatePrices
#5
0x6ad2e98b
· blocks 3
#9
execOrders
#10
execOrders
#13
0x59558d29
· blocks 1
#15
execOrders
· blocks 1
#16
aggregate3
#17
execFwdPositionOpsV2
#19
execFwdPositionOpsV2
#20
updateDataFeedsValuesPartial
#21
0x3f5c179b
#24
0x3f5c179b
· blocks 1
#25
0xd62522e3
#29
setData
· blocks 1
#31
execOrders
#32
execOrders
#33
execOrders
#34
execOrders
#6
0xab083028
· blocks 3
#11
0x5acec890
· blocks 3
#14
0x59558d29
#22
0x3f5c179b
#26
batchUpdate
#30
setData
#7
0xab083028
· blocks 1
#8
0x8263f5d9
#12
0x928e4afa
· blocks 1
#18
execFwdPositionOpsV2
#23
0x3f5c179b
#28
execFwdPositionOpsV2
#27
0xed82b078
#35
execOrders
· blocks 2
#36
execOrders
· blocks 1
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
7
w2
8
w2
11
w1
12
w2
13
w0
14
w1
15
w0
18
w2
22
w1
23
w2
24
w0
26
w1
27
w3
28
w2
29
w0
30
w1
35
w3
36
w4
37
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0xba33378a…f1df
0x34b655…2a6f
4 touches
1 conflict
0xc8cb0701…3926
0x34b655…2a6f
4 touches
1 conflict
0xdd9dc4b3…73b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
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:
Perpl
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity