pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,037,216
← previous block
next block →
recent activity
Analyzing
Block #71,037,216
10 transactions · 9 stateful · 2026-04-28 07:40:36 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,037,216
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x69f064ec
#5
0x6463ffd1
· blocks 1
#7
forward
#8
forward
#9
setData
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4ca4d087…6641
0x065c9d…c394
4 touches
1 conflict
0x57359607…d2cb
0x065c9d…c394
4 touches
1 conflict
0xc50beafa…4548
0x065c9d…c394
4 touches
1 conflict
0xc62e4805…1596
0x065c9d…c394
4 touches
1 conflict
0xda0fe9a1…b7bc
0x065c9d…c394
4 touches
1 conflict
0x823b9af4…62b1
0x065c9d…c394
2 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:
0xd0f8a642…83badc
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity