pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,908,789
← previous block
next block →
recent activity
Analyzing
Block #70,908,789
8 transactions · 7 stateful · 2026-04-27 17:25:26 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,789
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
updateDataFeedsValuesPartial
#3
0x0c7abd22
· blocks 1
#5
setData
#6
exactInputSingle
#7
updatePrices
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47d
0x1b6862…e19c
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xe0778da2…7806
0xa6afd3…d132
3 touches
1 conflict
0xa576576b…d8ed
0xd32edf…ff58
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity