pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,898,108
← previous block
next block →
recent activity
Analyzing
Block #74,898,108
12 transactions · 10 stateful · 2026-05-16 04:46:44 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,898,108
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
updatePrices
#4
supply
#5
updatePosition
#6
forward
#7
transfer
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#2
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x4aa4f53b…899f
0x188d58…ea8e
4 touches
1 conflict
0x4aa4f53b…89a1
0x188d58…ea8e
4 touches
1 conflict
0x120919d1…832d
0x386489…7508
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
2 touches
0 conflicts
0xaa608254…8646
0x57ea24…2cec
2 touches
0 conflicts
0x058d37c9…eba8
0x754704…b603
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:
USDC (USDC)
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity