pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,650,540
← previous block
next block →
recent activity
Analyzing
Block #74,650,540
13 transactions · 8 stateful · 2026-05-15 01:14:07 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,650,540
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0xed82b078
· blocks 1
#3
updatePrices
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
0xfd0a6d…77ed
#8
0x493b82…7c0a
#9
setData
#10
0x39435dac
#11
0x39435dac
#12
0x053c0052
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaaa91d19…c53e
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x2b5e5218…8f7b
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block
·
next block →
recent activity