pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,668,361
← previous block
next block →
recent activity
Analyzing
Block #76,668,361
9 transactions · 8 stateful · 2026-05-24 09:40:58 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,668,361
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
executeMetaTxn
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x785f5745
#8
0x39435dac
#3
0x669a7d5e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xfb7f6334…e9fe
0x000000…8ba3
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xa437a5ce…b8c6
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
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