pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,892,182
← previous block
next block →
recent activity
Analyzing
Block #70,892,182
12 transactions · 9 stateful · 2026-04-27 15:34:50 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,182
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xb3dd4ec4
#2
updatePrices
· blocks 3
#4
updatePrices
#7
updatePrices
#8
updatePrices
#9
updateDataFeedsValuesPartial
#10
setData
#11
updatePrices
#3
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
8 touches
6 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
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:
0xb857c13a…1a9be1
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity