pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,668,428
← previous block
next block →
recent activity
Analyzing
Block #76,668,428
9 transactions · 8 stateful · 2026-05-24 09:41:25 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,428
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0xe0bdc7…2e79
#4
0x5339c59f
#5
0x669a7d5e
· blocks 1
#7
setData
#8
0x6a12c83d
#6
0x669a7d5e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
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
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x14ba0e5f…a748
0x188d58…ea8e
2 touches
0 conflicts
0x14ba0e5f…a74a
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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