pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,878,171
← previous block
next block →
recent activity
Analyzing
Block #70,878,171
8 transactions · 8 stateful · 2026-04-27 14:01:36 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,171
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x6463ffd1
· blocks 1
#5
0x69ef6cb7
#6
approve
#7
updatePrices
#4
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xbc0bd68a…dcb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x01d4eb21…bb05
0x065c9d…c394
4 touches
1 conflict
0x0c9bde9a…352a
0x065c9d…c394
4 touches
1 conflict
0x32ef2ac5…ffae
0x065c9d…c394
4 touches
1 conflict
0xb305c877…b2ca
0x065c9d…c394
2 touches
1 conflict
0x62b2c923…04eb
0x065c9d…c394
2 touches
1 conflict
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:
0xd0f8a642…83badc
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity