pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,546,459
← previous block
next block →
recent activity
Analyzing
Block #97,546,459
12 transactions · 9 stateful · 2026-08-20 05:48:52 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,546,459
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
0x7b84f330
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x5acec890
#5
execFwdPositionOpsV2
#6
handleOps
#7
setData
#8
exactInputSingle
#9
0x59558d29
#10
execOrders
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xe9b7fd34…9b6a
0x065c9d…c394
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x064bb149…79fd
0x34b655…2a6f
2 touches
0 conflicts
0x44c1b819…8847
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x5dbcaf56…2e2f
0x34b655…2a6f
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:
0xc1570aa1…7ac91b
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity