pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,996,013
← previous block
next block →
recent activity
Analyzing
Block #70,996,013
13 transactions · 13 stateful · 2026-04-28 03:06:23 UTC
Parallelism
77
/100
Blocked
23
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,013
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x6463ffd1
· blocks 2
#7
setData
#10
0xed82b078
#11
updatePrices
#12
updatePrices
#3
updatePrices
#8
0xed82b078
· blocks 1
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
0x00000000…0012
0x1b6862…e19c
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:
0x065c9d28…a9c394
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity