pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,878,058
← previous block
next block →
recent activity
Analyzing
Block #70,878,058
13 transactions · 10 stateful · 2026-04-27 14:00:50 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,878,058
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ef6c8a
#2
updatePrices
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x98717539
· blocks 2
#7
0x6463ffd1
#8
0xb0435a94
#9
0x0c7abd22
#10
updateDataFeedsValuesPartial
#11
setData
#6
0x98717539
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x41335ddf…94b9
0x34b655…2a6f
4 touches
1 conflict
0x904fc3c0…00ec
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 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
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:
0x34b6552d…112a6f
1 conflict on slot
0x3254d19b21…baf714
Audit this contract →
← previous block
·
next block →
recent activity