pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,351,242
← previous block
next block →
recent activity
Analyzing
Block #74,351,242
9 transactions · 7 stateful · 2026-05-13 15:54:04 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
#74,351,242
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a049f14
#2
0x8263f5d9
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0175b7a6…1db9
0x5d823e…89c6
4 touches
1 conflict
0x0ef1e663…8f2a
0x5d823e…89c6
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x3cf2fdf6…f98f
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
0x5d823e99…9589c6
1 conflict on slot
0x0175b7a638…a01db9
Audit this contract →
← previous block
·
next block →
recent activity