pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,688,607
← previous block
next block →
recent activity
Analyzing
Block #73,688,607
9 transactions · 8 stateful · 2026-05-10 14:11:40 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,688,607
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a009293
#3
0x6a009293
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0712f8c5…2b65
0x065c9d…c394
2 touches
0 conflicts
0x72ff4682…5d4f
0x065c9d…c394
2 touches
0 conflicts
0x9bd14970…f24f
0x065c9d…c394
2 touches
0 conflicts
0xa3cf3a22…4f37
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0ac3194537…8f2c72
Audit this contract →
← previous block
·
next block →
recent activity