pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,062,580
← previous block
next block →
recent activity
Analyzing
Block #76,062,580
9 transactions · 6 stateful · 2026-05-21 14:26:52 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,062,580
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updatePrices
#3
addLiquidity
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x4ea53d…afc8
#8
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c499eb7…3824
0x5afd3e…7620
4 touches
1 conflict
0x31dc1ab1…a3df
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
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:
Liquidity Book Token (LBT)
1 conflict on slot
0x9c499eb714…b93824
Audit this contract →
← previous block
·
next block →
recent activity