pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,446,606
← previous block
next block →
recent activity
Analyzing
Block #73,446,606
15 transactions · 10 stateful · 2026-05-09 11:16:04 UTC
Parallelism
87
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,446,606
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#2
0x719d975a
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
setData
#11
updateDataFeedsValuesPartial
#12
0x69ff17eb
#13
0xe9316489
#14
0x39435dac
#4
updatePrices
#10
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0xae90535d…c14f
0xa6afd3…d132
3 touches
1 conflict
0xfad9a14f…3e89
0x065c9d…c394
2 touches
0 conflicts
0xc9e97522…3519
0x2a68ba…90c5
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0x110738b1…ed0c
0x754704…b603
2 touches
0 conflicts
0x1e349dde…a33a
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity