pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,469,881
← previous block
next block →
recent activity
Analyzing
Block #75,469,881
10 transactions · 6 stateful · 2026-05-18 20:27:36 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,469,881
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0xed82b078
#5
0x6a0b76b0
#6
0xfeee29…30d7
#7
0x3ebf3d…0483
#8
setData
#9
0x39435dac
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1540bf76…cdeb
0x065c9d…c394
2 touches
0 conflicts
0x82e99b90…38cd
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x89aebdc3…701c
0x065c9d…c394
2 touches
0 conflicts
0xb65f8dfc…f727
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity