pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,846,341
← previous block
next block →
recent activity
Analyzing
Block #70,846,341
11 transactions · 11 stateful · 2026-04-27 10:29:32 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,846,341
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x98717539
· blocks 1
#3
0x6463ffd1
#4
0x0c7abd22
#5
0xed82b078
· blocks 1
#7
setData
#9
updatePrices
· blocks 1
#6
0xed82b078
#8
0x39435dac
#10
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x2a354a63…0515
0x131a2e…0da9
4 touches
1 conflict
0xd984a5e4…5cfc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x0fff4a9f…b7f6
0x34b655…2a6f
2 touches
0 conflicts
0x27007746…0502
0x754704…b603
2 touches
0 conflicts
0x09000000…0001
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity