pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,429,878
← previous block
next block →
recent activity
Analyzing
Block #74,429,878
11 transactions · 10 stateful · 2026-05-14 00:37:31 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,429,878
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#3
0xcf7468f4
#4
updatePrices
· blocks 1
#6
0xa96df62f
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#2
0x1ffa3c9b
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0f673fd…37a7
0x5d823e…89c6
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x50997ada…364d
0x5d823e…89c6
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x3620fd3c…53a7
0x5d823e…89c6
2 touches
1 conflict
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
0xf0f673fde0…aa37a7
Audit this contract →
← previous block
·
next block →
recent activity