pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,908,790
← previous block
next block →
recent activity
Analyzing
Block #70,908,790
9 transactions · 7 stateful · 2026-04-27 17:25:26 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,908,790
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x98717539
· blocks 1
#5
0x0c7abd22
#6
forward
#7
0x3a022aa7
#8
setData
#4
0x98717539
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
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x12e7c471…901c
0x34b655…2a6f
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x6c042c61…f883
0x34b655…2a6f
2 touches
0 conflicts
0x6d732538…9d5e
0x34b655…2a6f
2 touches
0 conflicts
0x7b50a82b…f53d
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:
0x8d66a43f…113095
1 conflict on slot
0x8a35acfbc1…6bd1b0
Audit this contract →
← previous block
·
next block →
recent activity