pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,502,168
← previous block
next block →
recent activity
Analyzing
Block #74,502,168
10 transactions · 8 stateful · 2026-05-14 08:38:46 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,502,168
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x6a058a8d
#5
0x7f21c0…284b
#6
setData
#7
execute
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0xc12b04b0…884b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x9cafc3b6…ee8c
0x000000…012a
2 touches
0 conflicts
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
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:
0x34b6552d…112a6f
1 conflict on slot
0x5aed1bd252…0a7afa
Audit this contract →
← previous block
·
next block →
recent activity