pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,374,779
← previous block
next block →
recent activity
Analyzing
Block #73,374,779
9 transactions · 9 stateful · 2026-05-09 03:18:04 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,374,779
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
· blocks 1
#2
updatePrices
#3
addLiquidity
#4
updateDataFeedsValuesPartial
#6
0x69fea7e4
#7
0xeffdedb0
#8
setData
#5
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xbc47f4c7…ebe7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x83a78bec…0901
0x059114…ac3b
2 touches
0 conflicts
0x85632a1a…d074
0x059114…ac3b
2 touches
0 conflicts
0x9a2f1f95…0617
0x059114…ac3b
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xc3c8642ae9…317da5
Audit this contract →
← previous block
·
next block →
recent activity