pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,610,281
← previous block
next block →
recent activity
Analyzing
Block #74,610,281
13 transactions · 8 stateful · 2026-05-14 20:45:54 UTC
Parallelism
85
/100
Blocked
38
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,610,281
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 3
#3
removeLiquidity
#4
0x98717539
#5
0x62be7533
#6
0x0f6795d9
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#11
setData
#12
0x39435dac
#2
0x1094dc9f
#9
0x5339c59f
#10
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc179163f…b540
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x9164dfcc…c89d
0x065c9d…c394
3 touches
1 conflict
0xc2a2bf15…4d65
0x065c9d…c394
3 touches
1 conflict
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
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
0xc179163f78…f4b540
Audit this contract →
← previous block
·
next block →
recent activity