pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,217,945
← previous block
next block →
recent activity
Analyzing
Block #74,217,945
9 transactions · 7 stateful · 2026-05-13 01:07:43 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,217,945
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x6a03cf57
#2
0x0c7abd22
· blocks 1
#4
addLiquidity
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4b0f7031…c527
0xd32edf…ff58
3 touches
1 conflict
0xe4bd8398…d622
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x3af0dd8e…0028
0x1b6862…e19c
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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:
USDC (USDC)
1 conflict on slot
0x4039b31fcf…cb0f4a
Audit this contract →
← previous block
·
next block →
recent activity