pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,917,802
← previous block
next block →
recent activity
Analyzing
Block #70,917,802
11 transactions · 8 stateful · 2026-04-27 18:25:30 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,802
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
· blocks 1
#8
0x69efaa92
#9
setData
#10
0x39435dac
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2d2de50…c179
0xd32edf…ff58
3 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
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x268fa7a0…05bc
0x34b655…2a6f
2 touches
0 conflicts
0x39e44cfd…c435
0x34b655…2a6f
2 touches
0 conflicts
0x678143da…dc6b
0x34b655…2a6f
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:
0xd32edf66…9fff58
1 conflict on slot
0xa2d2de5046…39c179
Audit this contract →
← previous block
·
next block →
recent activity