pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,505,032
← previous block
next block →
recent activity
Analyzing
Block #98,505,032
28 transactions · 26 stateful · 2026-08-23 14:41:20 UTC
Parallelism
61
/100
Blocked
50
%
Avg conflicts / tx
1.11
Longest chain
11
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,505,032
· 28 txs across 11 waves · depth 11
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#3
0x6a8b0708
· blocks 1
#7
0xab083028
#10
0x6a8b0708
#12
execOrder
· blocks 2
#13
0x59558d29
#14
execPerpOps
#15
execPerpOps
#17
execFwdPositionOpsV2
· blocks 3
#18
execFwdPositionOpsV2
#19
0x3f5c179b
#22
forward
#23
0xed82b078
#24
setData
#2
0x0c7abd22
· blocks 4
#4
0x6a8b0708
#5
execOrders
· blocks 2
#11
crank
· blocks 1
#6
execOrders
· blocks 3
#20
0x0c7abd22
#8
execOrders
· blocks 2
#9
execOrders
· blocks 1
#16
execFwdPositionOpsV2
· blocks 3
#21
execFwdPositionOpsV2
· blocks 1
#25
execOrders
· blocks 2
#26
execOrders
· blocks 1
#27
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w2
6
w3
8
w4
9
w5
11
w2
12
w0
16
w6
17
w0
20
w3
21
w7
25
w8
26
w9
27
w10
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
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:
ShMonad (shMON)
6 conflicts on slot
0x0000000000…00001d
Audit this contract →
← previous block
·
next block →
recent activity