pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,779,463
← previous block
next block →
recent activity
Analyzing
Block #74,779,463
12 transactions · 9 stateful · 2026-05-15 15:35:23 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,779,463
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
· blocks 1
#6
updatePriceFeedsIfNecessary
#8
0xed82b078
· blocks 1
#10
setData
#11
0xb2e141…018d
#7
0x0c7abd22
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcfc12315…f972
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69e
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccb
0x2880ab…7b43
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity