pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,024,159
← previous block
next block →
recent activity
Analyzing
Block #76,024,159
8 transactions · 5 stateful · 2026-05-21 10:10:37 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,024,159
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
#5
0x0f6795d9
#6
0x0f6795d9
#7
setData
#2
swap
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
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x13c0ede5…0534
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4107a1af…0c26
0x065c9d…c394
2 touches
0 conflicts
0x5a1d2094…8a36
0x065c9d…c394
2 touches
0 conflicts
0x944abe60…57d6
0x065c9d…c394
2 touches
0 conflicts
0xe7db977f…0659
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x0aa885fa2f…33a3d1
Audit this contract →
← previous block
·
next block →
recent activity