pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,094,940
← previous block
next block →
recent activity
Analyzing
Block #71,094,940
13 transactions · 10 stateful · 2026-04-28 14:05:06 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
#71,094,940
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updatePrices
· blocks 1
#3
updatePrices
#5
0x69f0bf0a
#6
handleOps
#7
updateDataFeedsValuesPartial
#8
0x6463ffd1
· blocks 1
#10
relay
#11
0x69f0bf09
#12
setData
#4
updatePrices
#9
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x74a20704…7e31
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d19107e…5e6e
0x065c9d…c394
4 touches
1 conflict
0xaf98ee75…69e1
0x065c9d…c394
3 touches
1 conflict
0xea4caaba…7019
0x065c9d…c394
3 touches
1 conflict
0x960122fb…bccc
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity