pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,535,670
← previous block
next block →
recent activity
Analyzing
Block #77,535,670
12 transactions · 10 stateful · 2026-05-28 09:59:52 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,535,670
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0xed82b078
#4
0x0f6795d9
#5
0x0f6795d9
#6
setData
#7
updatePosition
#8
transfer
· blocks 1
#10
0xb947fe…9885
#11
0x39435dac
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x8d21ea8b…0572
0x34b655…2a6f
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
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity