pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,095,239
← previous block
next block →
recent activity
Analyzing
Block #71,095,239
11 transactions · 9 stateful · 2026-04-28 14:07:06 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
#71,095,239
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f0bf82
#2
multicall
#3
updatePrices
#4
0x69f0bf81
#5
updateDataFeedsValuesPartial
#6
setData
#7
handleOps
#8
0x98717539
#9
0x6463ffd1
· blocks 1
#10
0x6463ffd1
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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x96ae7474…8a08
0x065c9d…c394
4 touches
1 conflict
0x9822a980…2081
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x340ff8ac…1adc
0x065c9d…c394
3 touches
1 conflict
0xda13261e…da69
0x065c9d…c394
3 touches
1 conflict
0xdea783ba…ce75
0x065c9d…c394
3 touches
1 conflict
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity