pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,450,730
← previous block
next block →
recent activity
Analyzing
Block #74,450,730
13 transactions · 8 stateful · 2026-05-14 02:56:19 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,450,730
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
updatePrices
#3
updatePrices
#5
0x39abec6b
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x6a053a4b
#10
0x0b9275…3824
#11
0x7b19a3…24a4
#12
setData
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0230870e…327e
0x2ab50b…5c41
2 touches
0 conflicts
0x03cc6495…e829
0x2ab50b…5c41
2 touches
0 conflicts
0x080c1dbe…ba16
0x2ab50b…5c41
2 touches
0 conflicts
0x0ab26740…d451
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
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