pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,981,676
← previous block
next block →
recent activity
Analyzing
Block #70,981,676
8 transactions · 7 stateful · 2026-04-28 01:30: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,981,676
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x54390b8b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x0c7abd22
#7
0x39435dac
#2
0x42dd8743
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1a96039a…9ee0
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x437422fa…5293
0x0594c7…a3be
2 touches
0 conflicts
0x9e6b417c…a2ad
0x0594c7…a3be
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity