pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,227,293
← previous block
next block →
recent activity
Analyzing
Block #76,227,293
12 transactions · 10 stateful · 2026-05-22 08:44:14 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,227,293
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapWithBackendSignature
· blocks 1
#3
0xab083028
· blocks 2
#6
0xc5a04723
#7
updateDataFeedsValuesPartial
#8
setData
#9
exactInputSingle
#10
redeemDelegations
#11
execOrders
#2
0xd60faa87
#4
0x0c7abd22
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03226734…d6d2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x3df7769a…5d17
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
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-WETH/USDC
1 conflict on slot
0x03226734aa…71d6d2
Audit this contract →
← previous block
·
next block →
recent activity