pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,845,556
← previous block
next block →
recent activity
Analyzing
Block #70,845,556
11 transactions · 10 stateful · 2026-04-27 10:24:20 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,845,556
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
trade
#2
updatePrices
#3
0x15ea9545
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#7
setData
#8
0x39435dac
#9
updatePrices
#10
updatePrices
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3035b947…1a1d
0x065c9d…c394
4 touches
1 conflict
0x434eae84…88dd
0x065c9d…c394
4 touches
1 conflict
0x72c6181b…2653
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xa8d199cd…5024
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5d8373b9…233f
0x44b60b…f711
2 touches
0 conflicts
0x8956cb26…42f7
0x44b60b…f711
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
0x3035b9473d…771a1d
Audit this contract →
← previous block
·
next block →
recent activity