pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,262,426
← previous block
next block →
recent activity
Analyzing
Block #98,262,426
33 transactions · 28 stateful · 2026-08-22 18:19:17 UTC
Parallelism
70
/100
Blocked
68
%
Avg conflicts / tx
1.36
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,262,426
· 33 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
execute
#2
0xa96df62f
#3
0x7b84f330
· blocks 1
#4
0xab083028
· blocks 2
#6
0xab083028
#7
execOrders
· blocks 3
#10
execOrders
· blocks 5
#12
0x59558d29
#13
execPerpOps
#14
execPerpOps
#27
setData
#29
execOrders
#30
execOrders
#5
0xab083028
· blocks 2
#8
execOrders
· blocks 1
#11
execOrder
· blocks 3
#22
0x3f5c179b
#32
0x7b84f330
#9
execOrders
· blocks 1
#15
0x5acec890
· blocks 6
#23
0xed82b078
· blocks 1
#16
0x5acec890
· blocks 7
#25
0xed82b078
#17
0x5acec890
· blocks 3
#18
0x5acec890
· blocks 2
#19
0x928e4afa
· blocks 1
#20
execFwdPositionOpsV2
· blocks 3
#21
execFwdPositionOpsV2
· blocks 2
#28
execOrders
· blocks 1
#24
execFwdPositionOpsV2
· blocks 1
#31
execOrders
#26
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
7
w0
8
w1
9
w2
10
w0
11
w1
15
w2
16
w3
17
w4
18
w5
19
w6
20
w6
21
w7
22
w1
23
w2
24
w8
25
w3
32
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x077cfb7e…3f26
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 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
0x5d6da39762…d36c5c
Audit this contract →
← previous block
·
next block →
recent activity