pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,668,508
← previous block
next block →
recent activity
Analyzing
Block #76,668,508
10 transactions · 7 stateful · 2026-05-24 09:41:57 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,668,508
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x669a7d5e
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
0x785f5745
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#2
0x669a7d5e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1f7f6eb…f44d
0x754704…b603
4 touches
1 conflict
0x86a35e38…e53b
0x754704…b603
4 touches
1 conflict
0xc28a8689…d1b3
0x000000…8ba3
4 touches
1 conflict
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0001
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x8594c470…8975
0x065c9d…c394
2 touches
0 conflicts
0x8fa7a69c…8fd7
0x223a47…7777
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
0xb1f7f6ebf8…c6f44d
Audit this contract →
← previous block
·
next block →
recent activity