pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,922,819
← previous block
next block →
recent activity
Analyzing
Block #70,922,819
8 transactions · 7 stateful · 2026-04-27 18:58:53 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,922,819
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6463ffd1
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0x69efb264
#7
setData
#3
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d8a46f1…0d66
0x065c9d…c394
4 touches
1 conflict
0x38ee93d7…32e4
0x065c9d…c394
4 touches
1 conflict
0x61703ff2…cead
0x065c9d…c394
4 touches
1 conflict
0x8ca48a3e…5dd6
0x065c9d…c394
4 touches
1 conflict
0xe2e8270d…7d70
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
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
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity