pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,333,146
← previous block
next block →
recent activity
Analyzing
Block #75,333,146
12 transactions · 9 stateful · 2026-05-18 05:13:52 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,333,146
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x1094dc9f
· blocks 2
#3
0x0c7abd22
#5
0xc2d867a5
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#9
setData
#10
exactInputSingle
#11
execOrders
#4
0x62be7533
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeda72990…8c2a
0x065c9d…c394
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2f77f0f6…4a92
0x188d58…ea8e
2 touches
0 conflicts
0x2f77f0f6…4a93
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
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
0xeda72990c5…448c2a
Audit this contract →
← previous block
·
next block →
recent activity