pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,700,728
← previous block
next block →
recent activity
Analyzing
Block #75,700,728
13 transactions · 9 stateful · 2026-05-19 22:15:36 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
#75,700,728
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c652c…f312
#2
0x678292e2
#3
0xe2dc7dc3
#4
updateDataFeedsValuesPartial
#5
0x62be7533
· blocks 1
#6
0x0f6795d9
#7
0x0f6795d9
#8
updatePriceFeedsIfNecessary
#10
setData
#11
0x39435dac
#12
jMMeC
#9
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x15f5df3f…3971
0x1efe02…37d6
2 touches
0 conflicts
0xb61895cc…c538
0x1efe02…37d6
2 touches
0 conflicts
0xd39a0e9e…e29d
0x1efe02…37d6
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
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