pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,804,949
← previous block
next block →
recent activity
Analyzing
Block #73,804,949
7 transactions · 4 stateful · 2026-05-11 03:16:32 UTC
Parallelism
71
/100
Blocked
25
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,804,949
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
modifyLiquidities
· blocks 1
#3
setData
#4
0x26a54a…5657
#5
0xe86676…6906
#6
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x099ae7a3…4592
0x188d58…ea8e
2 touches
0 conflicts
0x099ae7a3…4593
0x188d58…ea8e
2 touches
0 conflicts
0x171593c9…c9c5
0x188d58…ea8e
2 touches
0 conflicts
0x22beb554…9f2a
0x188d58…ea8e
2 touches
0 conflicts
0x2f77f0f6…4a92
0x188d58…ea8e
2 touches
0 conflicts
0x2f77f0f6…4a93
0x188d58…ea8e
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:
0x754704bc…afb603
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity