pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,052
← previous block
next block →
recent activity
Analyzing
Block #70,878,052
9 transactions · 8 stateful · 2026-04-27 14:00:48 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,052
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x6463ffd1
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0x69ef6c88
#7
setData
#8
0x39435dac
#3
0x6463ffd1
· blocks 1
#4
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0de56a7e…728f
0x065c9d…c394
6 touches
3 conflicts
0x2f9e01e1…e43e
0x065c9d…c394
6 touches
3 conflicts
0x45407e2f…0bea
0x065c9d…c394
6 touches
3 conflicts
0x4bc881d3…03c8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
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:
0x065c9d28…a9c394
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity