pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,697,962
← previous block
next block →
recent activity
Analyzing
Block #73,697,962
8 transactions · 8 stateful · 2026-05-10 15:14:43 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,697,962
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#3
addLiquidity
#5
forward
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xaed1fa0f…08fa
0x34b655…2a6f
4 touches
1 conflict
0x4f483049…3cc7
0x34b655…2a6f
2 touches
0 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
2 touches
0 conflicts
0x6f067b71…bfef
0x34b655…2a6f
2 touches
0 conflicts
0xf6476f21…3580
0x34b655…2a6f
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
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:
Perpl
1 conflict on slot
0xd49762c96f…3b1359
Audit this contract →
← previous block
·
next block →
recent activity