pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,481,812
← previous block
next block →
recent activity
Analyzing
Block #76,481,812
8 transactions · 5 stateful · 2026-05-23 12:58:48 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,481,812
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidity
· blocks 1
#2
updateDataFeedsValuesPartial
#4
forward
#5
0x39435dac
#6
0xef00b5…d845
#7
setData
#3
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x16cf23e3…1241
0x5afd3e…7620
2 touches
0 conflicts
0xc0a2a720…10b9
0x5afd3e…7620
2 touches
0 conflicts
0xcd57b1b9…f4ed
0x5afd3e…7620
2 touches
0 conflicts
0xfcc81119…d3f2
0x5afd3e…7620
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
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity