pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,211,674
← previous block
next block →
recent activity
Analyzing
Block #73,211,674
14 transactions · 12 stateful · 2026-05-08 09:12:59 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
1.5
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,211,674
· 14 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
updatePrices
· blocks 6
#2
updatePrices
#6
updatePrices
#10
updateDataFeedsValuesPartial
#11
forward
#12
forward
#13
setData
#3
updatePrices
· blocks 5
#4
updatePrices
· blocks 4
#5
updatePrices
· blocks 3
#7
updatePrices
· blocks 2
#8
updatePrices
· blocks 1
#9
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
7
w4
8
w5
9
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000b
0x24b8be…7f9e
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
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
21 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity