pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,714
← previous block
next block →
recent activity
Analyzing
Block #71,421,714
11 transactions · 9 stateful · 2026-04-30 02:21:30 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,714
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
swapExactIn
· blocks 2
#3
0xcf7468f4
#4
addLiquidity
#5
0x0c7abd22
#7
swap
#8
0x6df9e92b
#9
updateDataFeedsValuesPartial
#10
setData
#2
0x76368669
· blocks 1
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d5bba53…fe58
0x065c9d…c394
5 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
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:
0x065c9d28…a9c394
3 conflicts on slot
0x8d5bba53c0…4afe58
Audit this contract →
← previous block
·
next block →
recent activity