pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,918,264
← previous block
next block →
recent activity
Analyzing
Block #74,918,264
14 transactions · 12 stateful · 2026-05-16 07:01:10 UTC
Parallelism
86
/100
Blocked
25
%
Avg conflicts / tx
0.21
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,918,264
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb264ae19
#2
0x42dd8743
· blocks 2
#3
updatePrices
· blocks 1
#5
0xccf50a51
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
0x0c7abd22
#11
updateDataFeedsValuesPartial
#12
setData
#13
jMMeC
#4
updatePrices
#9
0x62be7533
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
9
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3197c1bf…295b
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x7eb422cd…5924
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x3197c1bf60…6e295b
Audit this contract →
← previous block
·
next block →
recent activity