pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,469,972
← previous block
next block →
recent activity
Analyzing
Block #75,469,972
10 transactions · 8 stateful · 2026-05-18 20:28:12 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,469,972
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe2dc7dc3
#2
updateDataFeedsValuesPartial
#3
0x6df9e92b
· blocks 1
#5
0x5339c59f
#6
0x5339c59f
#7
setData
#8
0xb4e4c5…b71a
#9
0x39435dac
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24092f07…3a01
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x8361a5…7777
4 touches
1 conflict
0xf829b068…36cd
0x8361a5…7777
4 touches
1 conflict
0x00000000…0000
0x97dc05…7116
4 touches
1 conflict
0x00000000…0001
0x97dc05…7116
4 touches
1 conflict
0x749437cf…2fc0
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc1
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:
Wrapped MON (WMON)
1 conflict on slot
0x24092f0747…513a01
Audit this contract →
← previous block
·
next block →
recent activity