pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,891,536
← previous block
next block →
recent activity
Analyzing
Block #70,891,536
12 transactions · 10 stateful · 2026-04-27 15:30:31 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,891,536
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
· blocks 1
#4
rebalance
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
· blocks 1
#8
setData
#9
0x69ef818f
#10
updatePrices
#11
updatePrices
#3
updatePrices
#7
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x445a030a…1e0a
0x065c9d…c394
4 touches
1 conflict
0x5d3cd371…684a
0x065c9d…c394
4 touches
1 conflict
0xa111ca58…52ce
0x065c9d…c394
4 touches
1 conflict
0xca8a3eed…137b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xa9274bfd…c13d
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity