pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,552,657
← previous block
next block →
recent activity
Analyzing
Block #98,552,657
11 transactions · 10 stateful · 2026-08-23 18:49:49 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,552,657
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
0xab083028
#4
exactInputSingle
· blocks 1
#6
0x82f456…a0aa
#7
0x59558d29
#8
execFwdPositionOpsV2
#9
0x57368ddf
#10
setData
#5
exactInputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0003
0x86dfd5…6a7d
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0xa280fd2a…3fe0
0xb72e62…7777
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c4
0x1b6862…e19c
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:
Wrapped MON (WMON)
1 conflict on slot
0x1686502bc0…cfa1d2
Audit this contract →
← previous block
·
next block →
recent activity