pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,956,631
← previous block
next block →
recent activity
Analyzing
Block #70,956,631
8 transactions · 7 stateful · 2026-04-27 22:43:57 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,631
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 2
#4
0x6463ffd1
#5
updateDataFeedsValuesPartial
#6
setData
#7
cancel
#2
0x98717539
· blocks 1
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x143dba04…1b98
0x8d66a4…3095
6 touches
3 conflicts
0x1e451306…7993
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1af
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
6 touches
3 conflicts
0xe89e1a22…ce49
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x462c8be7…4f83
0x8d66a4…3095
4 touches
1 conflict
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
3 conflicts on slot
0x143dba04c2…a61b98
Audit this contract →
← previous block
·
next block →
recent activity