pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,878,538
← previous block
next block →
recent activity
Analyzing
Block #70,878,538
10 transactions · 9 stateful · 2026-04-27 14:04:02 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,538
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
setData
#7
exactInputSingle
#8
0x39435dac
#9
updatePrices
#5
0x6463ffd1
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
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x5b539f2f…46fa
0x065c9d…c394
3 touches
1 conflict
0x87a0d270…ad34
0x065c9d…c394
3 touches
1 conflict
0xa489ffbb…6d70
0x065c9d…c394
3 touches
1 conflict
0x8956cb26…42f7
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42f9
0x73ada1…8be0
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x2a354a6333…480515
Audit this contract →
← previous block
·
next block →
recent activity