pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,538,502
← previous block
next block →
recent activity
Analyzing
Block #98,538,502
11 transactions · 11 stateful · 2026-08-23 17:35:55 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,538,502
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
· blocks 1
#3
execOrders
· blocks 1
#4
0x59558d29
#5
0x5acec890
#6
0x928e4afa
#9
0x6a8b2ff3
#10
setData
#7
execFwdPositionOpsV2
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x14e61daa…db32
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0xfa95c964…d915
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity