pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,229,961
← previous block
next block →
recent activity
Analyzing
Block #76,229,961
10 transactions · 6 stateful · 2026-05-22 09:02:03 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,229,961
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
_makeSwaps
· blocks 1
#3
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x0f6795d9
#8
0xa1798512
#9
setData
#2
0xed82b078
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x728460b6…2cf0
0x065c9d…c394
3 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000c
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000d
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000e
0x2b37ef…0bdc
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xfe2bac2b2f…482cec
Audit this contract →
← previous block
·
next block →
recent activity