pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,210,814
← previous block
next block →
recent activity
Analyzing
Block #76,210,814
12 transactions · 10 stateful · 2026-05-22 06:54:05 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,210,814
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
swap
· blocks 2
#4
0xed82b078
#5
0x0c7abd22
#6
matchAdvancedOrders
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0xe9316489
#10
0xc10362…e771
#11
setData
#2
swap
· blocks 1
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x2d84d7…d457
6 touches
3 conflicts
0x00000000…0003
0x2d84d7…d457
6 touches
3 conflicts
0x00000000…0011
0x2d84d7…d457
6 touches
3 conflicts
0x00000000…001a
0x2d84d7…d457
6 touches
3 conflicts
0x00000000…0022
0x2d84d7…d457
6 touches
3 conflicts
0x099b88c6…2a8a
0x4917a5…1fe8
6 touches
3 conflicts
0x7ac76f4e…ad6b
0x188d58…ea8e
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 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:
AZND/AUSD (AZNDAUSD)
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity