pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,911,835
← previous block
next block →
recent activity
Analyzing
Block #70,911,835
10 transactions · 10 stateful · 2026-04-27 17:45: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
#70,911,835
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updatePriceFeedsIfNecessary
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
0xed82b078
· blocks 1
#8
0x69efa13f
#9
setData
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0xbbee74c2…567a
0x131a2e…0da9
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
2 touches
0 conflicts
0x32562817…845f
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42f7
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fa
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fd
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: MarginAccount
1 conflict on slot
0x4ab14837eb…ffe1b2
Audit this contract →
← previous block
·
next block →
recent activity