pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,041,970
← previous block
next block →
recent activity
Analyzing
Block #73,041,970
9 transactions · 7 stateful · 2026-05-07 14:23:50 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,970
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x6df9e92b
· blocks 1
#7
0x69fca0ee
#8
0xeffdedb0
#6
0x6df9e92b
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…0001
0x776059…1d8d
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0x09106a95…1467
0xeedfbc…f7dc
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x776059ee…881d8d
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity