pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,111,505
← previous block
next block →
recent activity
Analyzing
Block #76,111,505
13 transactions · 11 stateful · 2026-05-21 19:52:59 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,111,505
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
addLiquidity
· blocks 1
#4
execute
#5
0xed82b078
#6
0x0c7abd22
#7
redeemDelegations
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x6df9e92b
#11
setData
#12
redeemDelegations
#3
addLiquidityNATIVE
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
0x95ab51ba…ce60
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x53c935b1…5678
0x5afd3e…7620
4 touches
1 conflict
0x7ac2ca39…80c1
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0xb98b9e9d…a785
0x3bd359…433a
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
0x95ab51ba7e…70ce60
Audit this contract →
← previous block
·
next block →
recent activity