pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,562,416
← previous block
next block →
recent activity
Analyzing
Block #75,562,416
11 transactions · 10 stateful · 2026-05-19 06:52:39 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,562,416
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xbb5d006a
#2
0x2f745df6
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x785f5745
#7
0x6a0c092f
#8
setData
#9
deposit
· blocks 1
#10
deposit
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0c65a0…0852
4 touches
1 conflict
0x00000000…0003
0x0c65a0…0852
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x9be2b99a…a959
0x34b655…2a6f
2 touches
0 conflicts
0xd49762c9…1359
0x34b655…2a6f
2 touches
0 conflicts
0x4493caa6…32db
0x541997…f5a0
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:
0x0c65a0bc…0e0852
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity