pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,241,106
← previous block
next block →
recent activity
Analyzing
Block #74,241,106
10 transactions · 9 stateful · 2026-05-13 03:41:41 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,241,106
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xed82b078
· blocks 1
#6
0x6a03f36d
#7
setData
#8
swapAndForwardERC20
· blocks 1
#2
0x5bf9264c
#5
0xed82b078
#9
swapAndForwardERC20
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
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dff17e4…3fae
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x942644…91ab
4 touches
1 conflict
0x00000000…0003
0x942644…91ab
4 touches
1 conflict
0x00000000…0011
0x942644…91ab
4 touches
1 conflict
0x00000000…001a
0x942644…91ab
4 touches
1 conflict
0x00000000…001b
0x942644…91ab
4 touches
1 conflict
0x00000000…0022
0x942644…91ab
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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:
USDC (USDC)
1 conflict on slot
0x6dff17e4a6…1a3fae
Audit this contract →
← previous block
·
next block →
recent activity