pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,668,699
← previous block
next block →
recent activity
Analyzing
Block #99,668,699
25 transactions · 24 stateful · 2026-08-27 17:06:07 UTC
Parallelism
88
/100
Blocked
17
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,668,699
· 25 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0xab083028
· blocks 1
#6
execOrders
#7
0xb2d4797b
#8
0x59558d29
#9
execPerpOps
#10
execPerpOps
#11
updateDataFeedsValuesPartial
#13
execFwdPositionOpsV2
#14
executeBatch
#15
batchUpdate
#16
forward
#17
setData
#18
execOrders
#19
execOrders
#20
execOrders
#21
execOrders
#22
execOrders
#23
execOrders
#24
execOrders
#2
0x0c7abd22
· blocks 2
#4
0xab083028
#5
0x0c7abd22
#12
execFwdPositionOpsV2
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
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x04628dca…d8b9
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:
ShMonad (shMON)
3 conflicts on slot
0x0000000000…00002c
Audit this contract →
← previous block
·
next block →
recent activity