pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,333,588
← previous block
next block →
recent activity
Analyzing
Block #75,333,588
13 transactions · 12 stateful · 2026-05-18 05:16:49 UTC
Parallelism
77
/100
Blocked
17
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,333,588
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#4
0x5bf9264c
#5
0x366fe5db
#6
forward
#7
get_block_hash_257335279069929
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x6a0aa139
#11
setData
#12
0x39435dac
#2
execute
· blocks 1
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc1
0x2880ab…7b43
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
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)
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity