pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,472,009
← previous block
next block →
recent activity
Analyzing
Block #75,472,009
12 transactions · 7 stateful · 2026-05-18 20:41:45 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,472,009
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
0xed82b078
#6
0x6df9e92b
· blocks 1
#8
0x96b94c…9ba0
#9
0xfda66d…01be
#10
0xa18a1d…2e93
#11
0x39435dac
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
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
0x24092f07…3a01
0x3bd359…433a
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity