pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,986,680
← previous block
next block →
recent activity
Analyzing
Block #70,986,680
10 transactions · 9 stateful · 2026-04-28 02:04:12 UTC
Parallelism
50
/100
Blocked
44
%
Avg conflicts / tx
0.5
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,986,680
· 10 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
· blocks 2
#7
setData
#8
0x61633731
#9
0x39435dac
#3
0xed82b078
· blocks 1
#4
0xed82b078
· blocks 1
#5
0xed82b078
· blocks 1
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
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
0x01a89030…f786
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:
0x065c9d28…a9c394
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity