pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,951,519
← previous block
next block →
recent activity
Analyzing
Block #70,951,519
5 transactions · 5 stateful · 2026-04-27 22:09:55 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,519
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xb0435a94
· blocks 1
#4
setData
#3
0xb0435a94
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x311b76ee…5b8c
0x2e3234…7d90
2 touches
0 conflicts
0x4eb6e634…dcf4
0x2e3234…7d90
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x754704bc…afb603
1 conflict on slot
0xa3dc6f3549…9513e9
Audit this contract →
← previous block
·
next block →
recent activity