pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,201,679
← previous block
next block →
recent activity
Analyzing
Block #75,201,679
13 transactions · 10 stateful · 2026-05-17 14:34:35 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,201,679
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
· blocks 1
#4
forward
#5
forward
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x32f13f…ce0c
#10
0x8385e3…9ca0
#11
setData
#12
execOrders
#3
execute
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
6
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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x09330b0e…6424
0x065c9d…c394
2 touches
0 conflicts
0x293f8f87…626b
0x065c9d…c394
2 touches
0 conflicts
0x557fb997…d013
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:
USDC (USDC)
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity