pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,858,655
← previous block
next block →
recent activity
Analyzing
Block #94,858,655
14 transactions · 11 stateful · 2026-08-10 19:28:05 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,858,655
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a7a26bd
#2
0xab083028
#3
updatePrices
#4
updatePrices
#5
exactInputSingle
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
0xed82b078
#9
execFwdPositionOps
#10
updateDataFeedsValuesPartial
#11
setData
#12
execOrders
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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:
Perpl
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity