pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,196,745
← previous block
next block →
recent activity
Analyzing
Block #75,196,745
9 transactions · 6 stateful · 2026-05-17 14:01:37 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,196,745
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xccf50a51
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x8263f5d9
#6
setData
#7
swapExactIn
· blocks 1
#8
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f478f26…9d56
0x000000…012a
4 touches
1 conflict
0x9cafc3b6…ee8c
0x000000…012a
4 touches
1 conflict
0x00000000…0036
0x386489…7508
4 touches
1 conflict
0x1a920eda…bfae
0x386489…7508
4 touches
1 conflict
0x71ddb199…a2d9
0x754704…b603
4 touches
1 conflict
0xa8669ab5…6af7
0x754704…b603
4 touches
1 conflict
0x00000000…0036
0x784999…1f2d
4 touches
1 conflict
0x2f417c04…a545
0x784999…1f2d
4 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:
0x00000000…a9012a
1 conflict on slot
0x8f478f26db…3f9d56
Audit this contract →
← previous block
·
next block →
recent activity