pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,124
← previous block
next block →
recent activity
Analyzing
Block #70,878,124
10 transactions · 9 stateful · 2026-04-27 14:01:17 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,124
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
receiveMessage
#4
claimRewards
· blocks 1
#5
0x6463ffd1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
delegate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
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
0x12cf7ab9…b6aa
0x73ada1…8be0
2 touches
0 conflicts
0x2a675b6e…26ee
0x73ada1…8be0
2 touches
0 conflicts
0x34981793…5620
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:
0x00000000…001000
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity