pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,960,273
← previous block
next block →
recent activity
Analyzing
Block #73,960,273
9 transactions · 8 stateful · 2026-05-11 20:30:48 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,960,273
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
#2
0x5de3085d
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0x6a023cf0
#7
setData
#8
0x39435dac
#3
0x6df9e92b
· blocks 1
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x7b1b74a7…9206
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x41be85…e2bd
4 touches
1 conflict
0x00000000…0001
0x41be85…e2bd
4 touches
1 conflict
0x072430d8…35ad
0xed8924…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xed8924…7777
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
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)
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity