pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,553,961
← previous block
next block →
recent activity
Analyzing
Block #77,553,961
10 transactions · 9 stateful · 2026-05-28 12:01:40 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,553,961
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#4
0xe0de3ed7
#5
removeLiquidity
#6
updatePrices
#7
updateDataFeedsValuesPartial
#8
forward
#9
setData
#2
0x0c7abd22
· blocks 1
#3
0x9609049f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x298b534c…48af
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x403da190…be0d
0xd32edf…ff58
3 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x45474a6a…927d
0x188d58…ea8e
2 touches
0 conflicts
0x45474a6a…927e
0x188d58…ea8e
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x298b534c09…ce48af
Audit this contract →
← previous block
·
next block →
recent activity