pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,559,606
← previous block
next block →
recent activity
Analyzing
Block #98,559,606
11 transactions · 9 stateful · 2026-08-23 19:26:06 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,559,606
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
exactInputSingle
#4
0x9fc112…a625
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
0x6a8b49c6
#8
setData
#9
0x96598f…d28a
#10
execOrders
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x0e97d88f…b36f
0x34b655…2a6f
2 touches
0 conflicts
0x0f82d0e0…cffe
0x34b655…2a6f
2 touches
0 conflicts
0x2aab0897…78f7
0x34b655…2a6f
2 touches
0 conflicts
0x2b8ae238…b119
0x34b655…2a6f
2 touches
0 conflicts
0x1686502b…a1d2
0x3bd359…433a
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: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity