pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,332,605
← previous block
next block →
recent activity
Analyzing
Block #75,332,605
10 transactions · 8 stateful · 2026-05-18 05:10:13 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,332,605
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
transfer
#3
0xed82b078
· blocks 1
#5
verifyOracleProofV2
#6
updateDataFeedsValuesPartial
#7
0x6a0a9fad
#8
setData
#9
execOrders
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xc3e9fea8…1f78
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x516a2c81…8add
0x065c9d…c394
2 touches
0 conflicts
0x5b910f61…5d18
0x065c9d…c394
2 touches
0 conflicts
0x9856b9ad…bca5
0x065c9d…c394
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
0xfcb7b8b239…6bebb3
Audit this contract →
← previous block
·
next block →
recent activity