pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,641,127
← previous block
next block →
recent activity
Analyzing
Block #73,641,127
8 transactions · 7 stateful · 2026-05-10 08:51:23 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,641,127
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x39435dac
#4
setData
#5
0x98717539
· blocks 1
#7
exactInputSingle
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10f5f4d8…572e
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x689cd5fd…5556
0x34b655…2a6f
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
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:
0x34b6552d…112a6f
1 conflict on slot
0x10f5f4d8d3…cc572e
Audit this contract →
← previous block
·
next block →
recent activity