pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,067,796
← previous block
next block →
recent activity
Analyzing
Block #98,067,796
37 transactions · 31 stateful · 2026-08-22 01:59:20 UTC
Parallelism
76
/100
Blocked
52
%
Avg conflicts / tx
1.05
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,067,796
· 37 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
0x0c7abd22
· blocks 3
#4
0x7b84f330
· blocks 1
#5
0x41a8f47c
#6
0x41a8f47c
#7
execOrders
· blocks 6
#10
0x8263f5d9
#11
execOrder
#12
0x59558d29
#14
execPerpOps
#15
0x6b8f732b
#16
0x6b8f732b
#17
0x5acec890
· blocks 3
#21
0x6b8f732b
#22
artefact_keep
#23
execFwdPositionOpsV2
#24
0x3f5c179b
#25
batchUpdate
#28
forward
#29
setData
#30
0x61b316…130e
#2
0x0c7abd22
· blocks 3
#8
execOrders
· blocks 2
#18
0x5acec890
· blocks 2
#36
0x7b84f330
#3
0x0c7abd22
· blocks 2
#9
execOrders
· blocks 2
#13
0x6e1f3a01
#19
0x928e4afa
· blocks 3
#20
0x0c7abd22
· blocks 2
#26
0xed82b078
#27
execFwdPositionOpsV2
#31
execOrders
· blocks 4
#32
execOrders
· blocks 3
#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
2
w1
3
w2
4
w0
7
w0
8
w1
9
w2
13
w2
17
w0
18
w1
19
w2
20
w3
26
w3
27
w3
31
w4
32
w5
34
w7
35
w8
36
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity