pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,576,756
← previous block
next block →
recent activity
Analyzing
Block #98,576,756
10 transactions · 10 stateful · 2026-08-23 20:55:44 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,576,756
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
exactInputSingle
· blocks 1
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
setData
#8
conquer
#9
execOrders
#4
exactInputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0003
0x86dfd5…6a7d
4 touches
1 conflict
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
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:
0x86dfd554…906a7d
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity