pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,956,885
← previous block
next block →
recent activity
Analyzing
Block #70,956,885
9 transactions · 8 stateful · 2026-04-27 22:45:38 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,885
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
0x42bbae7a
· blocks 1
#5
updateTemporalNumericValuesV1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#4
mint
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
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x1925244e…7a94
0x188d58…ea8e
2 touches
0 conflicts
0x1925244e…7a95
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x37608aa2…2169
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:
0x00000000…a9012a
1 conflict on slot
0x18aed20c69…4f48f3
Audit this contract →
← previous block
·
next block →
recent activity