pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,877,862
← previous block
next block →
recent activity
Analyzing
Block #70,877,862
11 transactions · 9 stateful · 2026-04-27 13:59:32 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,862
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x2d9c6e…faad
#6
setData
#7
updatePosition
#8
0xed82b078
#9
0xed82b078
· blocks 1
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
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
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2af5f63a…b7b9
0x2e3234…7d90
2 touches
0 conflicts
0x4d017ee7…3542
0x73ada1…8be0
2 touches
0 conflicts
0x4f3acb5b…7c86
0x73ada1…8be0
2 touches
0 conflicts
0x6abb9910…d1ea
0x73ada1…8be0
2 touches
0 conflicts
0x6ed41474…b9ba
0x73ada1…8be0
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