pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,701,380
← previous block
next block →
recent activity
Analyzing
Block #71,701,380
10 transactions · 10 stateful · 2026-05-01 09:27:31 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,380
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf99cae99
#2
updatePrices
#3
0x9036287a
· blocks 1
#4
0xeffdedb0
#6
handleOps
#7
updateDataFeedsValuesPartial
#8
setData
#9
approve
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b298cd…94d0
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x15915b5c…c848
0x065c9d…c394
4 touches
1 conflict
0x9c796ce1…35c1
0x065c9d…c394
2 touches
0 conflicts
0xf8127de7…d5ec
0x3bd359…433a
2 touches
0 conflicts
0x5b4b3fa7…2f73
0x754704…b603
2 touches
0 conflicts
0x6bf588e3…ba89
0x754704…b603
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
1 conflict on slot
0xe8b298cd44…3d94d0
Audit this contract →
← previous block
·
next block →
recent activity