pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,964,224
← previous block
next block →
recent activity
Analyzing
Block #73,964,224
9 transactions · 7 stateful · 2026-05-11 20:57:05 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,964,224
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaa0506cd
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
setData
#7
0x39435dac
#8
jMMeC
#2
0xaa0506cd
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x29845d54…c9e4
0xa7283d…0ace
4 touches
1 conflict
0x29845d54…c9e5
0xa7283d…0ace
4 touches
1 conflict
0x29845d54…c9e6
0xa7283d…0ace
4 touches
1 conflict
0x29845d54…c9e7
0xa7283d…0ace
4 touches
1 conflict
0x8fa7a69c…8fd7
0xbbc116…7777
4 touches
1 conflict
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