pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,072
← previous block
next block →
recent activity
Analyzing
Block #70,878,072
11 transactions · 9 stateful · 2026-04-27 14:00:56 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,072
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
#5
0x0c7abd22
· blocks 2
#6
setData
#9
0x39435dac
#10
updatePrices
#7
0x0c7abd22
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc877b08e…97a2
0xd32edf…ff58
5 touches
3 conflicts
0x4d10fad4…b8e0
0x3bd359…433a
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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
3 conflicts on slot
0x0000000000…000012
Audit this contract →
← previous block
·
next block →
recent activity