pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,846,379
← previous block
next block →
recent activity
Analyzing
Block #70,846,379
15 transactions · 15 stateful · 2026-04-27 10:29:47 UTC
Parallelism
87
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,846,379
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
multicall
· blocks 1
#4
updatePrices
#5
0x98717539
· blocks 1
#6
setData
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6463ffd1
#10
0x6df9e92b
#11
0x69ef3b12
#13
updatePrices
#14
updatePrices
#3
multicall
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd984a5e4…5cfc
0x34b655…2a6f
4 touches
1 conflict
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
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
0xd984a5e4e9…3a5cfc
Audit this contract →
← previous block
·
next block →
recent activity