pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,901,325
← previous block
next block →
recent activity
Analyzing
Block #74,901,325
13 transactions · 9 stateful · 2026-05-16 05:08:12 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,901,325
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a07fc33
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#9
setData
#10
execOrders
#11
execOrders
#12
execOrders
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x15b502e2…2a87
0x065c9d…c394
2 touches
0 conflicts
0x1db0647a…f961
0x065c9d…c394
2 touches
0 conflicts
0x3343b2ef…d711
0x065c9d…c394
2 touches
0 conflicts
0x6481c337…49f5
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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity