pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,917,855
← previous block
next block →
recent activity
Analyzing
Block #70,917,855
9 transactions · 7 stateful · 2026-04-27 18:25:51 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,855
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 1
#5
setData
#7
forward
#8
0x69efaaa7
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef75b7d3…a98e
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
0x6eba5e7f…4b52
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
2 touches
0 conflicts
0xc3aacf13…6b3d
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
0xef75b7d350…96a98e
Audit this contract →
← previous block
·
next block →
recent activity