pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,322,048
← previous block
next block →
recent activity
Analyzing
Block #93,322,048
13 transactions · 12 stateful · 2026-08-05 10:22:55 UTC
Parallelism
69
/100
Blocked
25
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,322,048
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
transfer
· blocks 3
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
approve
#8
updatePriceFeedsIfNecessary
#9
executeBatch
#10
0x0f6795d9
#11
0x0f6795d9
#12
setData
#2
transfer
· blocks 2
#3
transfer
· blocks 1
#4
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeaced15b…2221
0x754704…b603
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x91855e…ac7e
2 touches
0 conflicts
0x0cfb5d79…7ccb
0xb754ba…508d
2 touches
0 conflicts
0x0cfb5d79…7ccc
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1a
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1b
0xb754ba…508d
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:
USDC (USDC)
6 conflicts on slot
0xeaced15b26…bf2221
Audit this contract →
← previous block
·
next block →
recent activity