pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,995,069
← previous block
next block →
recent activity
Analyzing
Block #70,995,069
11 transactions · 9 stateful · 2026-04-28 03:00:05 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,069
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0x6463ffd1
#3
0x0c7abd22
· blocks 1
#4
mintCube
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#9
updatePrices
#10
updatePrices
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x81bc02a7…52cf
0xd32edf…ff58
3 touches
1 conflict
0x317f6232…8a4c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x1195cf…64b7
2 touches
0 conflicts
0x2bf9e449…5c20
0x065c9d…c394
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…000012
Audit this contract →
← previous block
·
next block →
recent activity